website

profileemey.b
sdis_group_project_v1.2.docx

Running head: SDIS INFORMATIVE ONLINE RESOURCE CENTER

SDIS Informative Online Resource Center 74

Capstone Project

SDIS Informative Online Resource Center

By

Christopher Millard, Emery Bullock, Hau Le, Hector Roman, & Swetha Yarra

Professor Lu Zhang

10/24/2016

Version History

Version #

Created

By

Revision

Date

Approved

By

Approval

Date

Reason

1.0

Hau Le

09/06/2016

Project Team

09/07/2016

Milestone 1

1.1

Hau Le

09/20/2016

Project Team

09/21/2016

Milestone 1 & 2

1.2

Chris Millard

10/9/2016

Project Team

10/10/2016

Milestone 1, 2, & 3

1.3

Hau Le

10/23/2016

Project Team

10/24/2016

Milestone 1, 2, 3, & 4

Executive Summary

Life of an international student in America can be tough. An international student has to deal with different types of challenges such as financial, cultural, social, and academic. Living in a new country, trying to understand a new culture, and speaking a different language can be tough. Small tasks such as finding textbooks for classes, looking for a tutoring service, renting a car could become more difficult than expected. In addition, a new college student in San Diego will need to absorb much information rapidly to adapt to the new environment and avoid being clueless and confused about the upcoming challenging college life. As a solution, this project aims to develop and fulfill a user-friendly, practical online resource center for international students in San Diego.

Table of Contents

Project Vison 6

Overview Statement 6

Problem 6

Solution 6

Stakeholders 7

Benefits 8

Project Feasibility 8

SWOT Analysis 9

Strength 10

Weakness 11

Opportunities 11

Threat 11

Project Scope 12

Project Phases 13

Team Structure and Capabilities 19

Functional Requirements & Requirements Traceability Matrix 22

Nonfunctional Requirements 25

SEO 25

Maintainability 26

Security 27

Project Management 27

Project Plan 29

Project Work Breakdown Structure (WBS) 30

Project Schedule 33

Risk Management 33

Risk Breakdown Structure 34

Risk Analysis 35

Risk Assessment 37

Risk Reporting 39

Risk Severity Matrix & Urgency Response Plan 39

Contingency Plan 41

Problem Analysis 42

Website Design 43

Website Mockups 43

Website Use Cases 48

Database Design 50

Data Flow Diagrams 50

ER Diagram 51

Database Tables 52

Quality Assurance 53

Test Plan Process 53

Error Checking 54

Technical Control Process 55

Change Management Process 55

Website Test Plan 57

Testing Guidelines 57

Browser Performance Testing Missing 58

Usability Testing Incomplete 58

Functionality Testing Missing 59

Project Implementation 59

Website Recovery Plan Missing 59

Project Completion 59

Lessons Learned Missing 59

Project Conclusion Missing 59

Appendices 59

Appendix A: Website Usability Testing Survey Questions 59

Appendix B: Detailed Change Management Plan 61

Appendix C: Project Meeting 65

References 76

Table of Figures Missing

Project Vison

The internet has a vast knowledge base. There are many things which a student can learn by performing a simple search on the internet. However, not all information found on the internet is considered reliable and relevant. The project team will create and implement a website. The website, which is registered and functioning as www.sdishub.com, is an informative online resource center that can be used by international students who are currently studying in San Diego. The project vision is to help guide the organization become a more cause-driven business. The objective is not only providing an informative online resource center but also contributing significantly to the growth and success of the community of international students in San Diego.

Overview Statement

Problem

Today, education has risen and this has affected international students. The manner and ability to use local education centers influence the necessity to transverse over international boundaries. The rise in the number of international studies has surpassed how students develop, process their applications and receive instant information on the level to communicate and increase interactions in the local and international colleges (Saw, Abbott, Donaghey & McDonald, 2013). Thus, there is a lack of enough information to inform and offer support for the local and international studies. This is a challenge that affects the ability, requirement, and means to offer credible information to international students.

Solution

The development of the international gateway website is a comparative solution that focuses on international students. The use of this website will focus not only on the local (the main purpose is for international students, right?) but also for international students who could like to use the services of the university website (not sure if I understand this –we’re talking about the website we’re developing) in writing and posting application letters. More important, these international students require information and other important need for developing and leading their educational needs (Saw, Abbott, Donaghey & McDonald, 2013). It is, therefore, essential to offer, create, and allocate essential facts to support and help students make essential decisions about their favorite colleges for study. Although this is a pathway, it is also a link that expresses (don’t quite understand what is being expressed here) information for students to acquire the services and functional information for their needs.

Stakeholders

The main stakeholder (there are multiple stakeholders) includes the university’s academic and international student’s coordinators. They are the main stakeholders who are pushing for the development of such website that could help the university in attracting and retaining international based students. It is also essential in leading, promoting, and supporting the international student’s leaders in the university (don’t understand). As a coordinator for the international studies, we advocate and create the role of promoting diversity through gaining and leading a normal ability to elaborate (not sure what is being said here) and influence the ability for international students to learn and study (Saw, Abbott, Donaghey & McDonald, 2013). Therefore, it is essential in supporting and influencing the role of as: which the community is essential in supporting, gaining, and promoting the value based on the university’s culture.

Benefits

There are many benefits the university and stakeholders will gain in developing this website. The international students studying in the university will gain a resource for communicating and information dissemination in the community. More important, it will a portal for communication and informing the international students on the requirement and means of supporting the community’s role in supporting and influencing the community of its students (Saw, Abbott, Donaghey & McDonald, 2013). Gathering of international students will be critical to the success and ability to learn, promote, and ensure there is a growth based on improving student retention in the community and supporting the role of the community to a more productive society.

Project Feasibility

Our team conducted a feasibility study to help decide if the proposed project could be implemented successfully and in scope. The study considered items such as available technology, market staffing, and our time constraints. Figure 1.0 shows the items we considered during our study.

Image result for feasibility study process

Figure 1: Feasibility Study

SWOT Analysis

Strength

Threat

· Experienced Team

· Adequate Resources (Network, and Financial)

· Underserved market

· Low startup/maintenance/operating cost

· Competition

· Startup Risk

· Privacy Concerns

· Changes in laws

Weakness

Opportunities

· No copyrights

· No custom domain name

· Customer concerns

· Limited advertising

· Large Number of schools

· Diverse San Diego Culture

· Use of data to market other services

· Expansion into other cities

· High availability

· Social Organization/Social Entrepreneur

Strength

· The project team is made up of five individuals with experience that cover various markets. All team members hold bachelor’s degrees with two holding Masters degrees. The team also has team members that are certified in Agile. Combined the team has over 50 years of work experience with most of the experience coming in the Information Technology Industry and Project Management.  

· The project team also has a vast network. This network will be a great asset when designing the website and marketing. The team also has enough capital resources to fund the project from design to implementation.

· There are currently other sites that are geared towards the international students. However, the majority of the site is geared to the entire market. Sites that are geared to a specific locality are underserved.

· Low startup and maintenance cost. The website offers low startup cost along with low maintenance cost.  

Weakness

•   The biggest weakness affecting our project is the lack of identity and an unknown entity.

Fulfilling a solid and effective marketing plan can reduce these weaknesses. •   Some customers will be cautious with using our site with concerns about the authenticity of our site.

Opportunities

•   There are a number of schools in the San Diego area that are popular with International

Students, this increases the number of potential partners. •   San Diego has a vast and diverse culture which makes it an attractive destination for

International Students. •   By utilizing the data gathered from our members and our sites traffic will allow us to utilize

the data to sell advertising space as well in future marketing campaign.

•   Our site with is available 24/7 which will accommodate a user from multiple time zones.

Threat

•   With any startup, there are always challenges. These challenges mostly come from the

unknown. These unknown factors come from issues that might arise during the project. 2016

is a Presidential Election year. One of the biggest issues in this year’s election is

immigrations. The result of the election may affect the number of new

international students entering the San Diego market.  

•   There is competition in this market. There is nothing that is currently keeping additional

competitors from entering the market.  

•   Privacy concerns will also be an issue. Users will want to protect their privacy and their personal information.  

Project Scope

The key objective of this project is to create a practical and useful online resource center. Our target users will be international students who are studying in San Diego area. Users will have the ability to search for links related to different topics such as universities and colleges in San Diego, Transportation (both public, and car rental services), library locations, housing service, tutoring service, and online book/school supply stores. Users can recover their login passwords in case of losing or forgetting. In addition, a user can also create or edit blogs on the website.

Guiding principle for this project:

· Cost effective

· User-friendly interfaces

· Easy Navigation

· Quick, simple, and efficient on-site search engine

· Capable of handling the web traffic

· Room for improvement (new functions/features or web application add-ons)

Considerations for future expansions and upgrade projects:

· Users can register via social media such as Twitter or Facebook

· Adding webstore for textbooks and school supplies (payable via PayPal or credit cards)

· Development of a mobile app (android or iOS platform) for the website

· Integrating off-site search engine such as Google or Bing to the website

· Improving online support by providing live chat feature

Project Phases

In the present Capstone project, the website design and development process will be done in Six different phases. The basic design of the project has the following steps:

1. Initiating & Planning

2. Designing

3. Developing

4. Testing & Documenting

5. Implementation

6. Post-Implementation

Phase One: Initiating & Planning

To initiate the project and designing a successful website, we need to gather the information related to the website development. How the website looks like, what information is provided on the websites and who are the users, and what content should be provided to the targeted audience.

According to our project scope, the website for the International Students provides information about universities in San Diego area where they can pursue their majors, they can get the details about the neighborhood where the International students reside. This website also provides information regarding the transportation and commuting facilities in San Diego. It also gives details about students’course textbooks which are sold online at the lesser price. The website also gives information about local recreation centers in San Diego area. This is the objective of the project.

Using the information gathered from phase one it is the time to put together to plan for the website. In this phase, where a site map is developed. The main topic areas of the site are enlisted in the site map, as well as sub topics if applicable. This serves as a guide on what content will be on the site and is essential to develop and understand navigational system. While the end user of the website (customer), needs to have to be in mind while designing the site, as a good user interface will create an easy way to navigate the website, and is the basis for this. During this planning phase, web designer needs to decide which technologies should be implemented.

Phase Two: Designing

This is the most crucial step for the project as we will create the prototype of the website based on the information gathered as per the requirements of the project. The target audience is one of the key factors considered. As part of the design phase in this phase communication between designer and the project manager which are crucial to ensure that the final website will match the needs and taste. It is important that you work closely with the designer, and exchanging ideas until the final design of the website is done.

Phase Three: Developing

It is the phase where the final website is created in this level. The website will take all the individual graphic elements from a prototype and use them to create the final functional site. It is the shell which serves as a template for a content page which will contain the main navigational structure for the website. On the technical side, the website requires an understanding of front-end web development.

Phase Four: Testing and Documenting

This is the phase where the web designer will attend to the final details and test the website. They test complete functionality of forms or other scripts as well last testing for last minute compatibility issues ensuring that website is optimized which helps while checking for issues such as cross- browser compatibility. Once the final approval for the web designer is done, it is the time to deliver the site. The domain name and web hosting services are setups, later the Search Engine Optimization of the website like title, description is integrated.

Phase Five: Implementation

Our project is an informative site which gives all the details to the International Student in San Diego. The information is related to the various universities in San Diego, housing, books related to the course. Our website will direct the user to the related website where he can find all information at one site. A single click on the website will redirect them to the particular website of a university or book rental site or the housing site.

In the present project as we just have three months of time-period, and we choose Wix to create our website as we have a simple drag and drop technology as we do not have programming background. As the first Beta version of Wix which released in 2008, it is not a newcomer to the website creation arena. But Wix is free, premium plans which start at a very less affordable price of 5$ per month has reinvented itself.

With the new Wix, we can create a modern looking business website without writing a single line of code or without running a Flash. It had ready- made HTML5 templates, which are the single- page personal profile templates, and does not contain content management systems. The simple method to set up website builder is to choose a template and start working on the content of the page and images. Developing a website is very easy with drag and drops method and affordable and can get the first version of the website in a very short time. Wix covers all the basic SEO settings is Google friendly and allows creating custom web page addresses.

Implementation part in the website creation includes various steps:

The Definitive Checklist

The initial phase of creating the website is to make the checklist of the requirements. Below is the list of the things needed to build a functional website:

Domain Name. This is the first thing we need to choose before starting the website. Domain name is the digital address that people will use to get connected to the website. The domain name of our website is “www.sdishub.com”

1. Choosing a website building Software. In this project, we choose Wix as website builder software. It has more features and tools of drag-and-drop website builders. The main reason for choosing Wix for building our website is it supports and has ability of e-commerce, online booking abilities, online portfolio, blog, and also can create a business website, where we can get basic version comes standard It requires No code knowledge. It is a one-click installation for third party app; we can customize page layout design. It is easy to design elements like an image slider, textbox, tabs, and elements. This website builder has an option to add, edit, and remove content like text and images, it can also add, edit, and remove blog posts. There will be a full level of technical support with email, phone, forum, and knowledge base.

All the technical issues like hosting, security, app compatibility issues are all dealt by Wix so there is no need to worry. The basic budget for developing the website through Wix, minimum startup cost for Connect Domain it is $4.08, Combo is $9.75, if it is Unlimited is $ 12.92, for e-commerce site $16.58. It has all hosting for the website, security, technical support is also included. There is an optional cost for the apps it can be either paid or free.

2. Website Hosting and Technical De. It is the storage unit where all the website content will be online. When the user types the domain name into the web browser, it will fetch website content from website host. Initially for the project, we want to use free hosting. Once we get the better idea about the traffic then we can shift to VPS hosting.

It will also help in managing technical issues such as security upgrades, and it ensires that the website works properly. But, Wix does not have an export feature. Basically, we cannot take the website out of Wix as the website is been maintained by the Wix administrator.

3. Website Template Design. Our website has a template design of the home page tab, university, housing, recreation, textbook, and contact us. The home page gives a brief explanation of the website and the blog. The different tab leads to the subpage of Housing where the international students can get information about the accommodation, rental apartments in San Diego. The University tab will give information about the different universities in San Diego. Recreation is the tab, which gives information about the travel spots in this area. The textbook tab will give information about the different textbooks related with the different courses and the rental websites, which provide the online purchase of books.

Phase Six: Post-Implementation

Once the website is created it is the responsibility of the organization to make things secure and maintenance. This can be in terms of upgrading the site, security issues and about data backup.

Team Structure and Capabilities

Figure 2: Project Team Organizational Chart

Figure 2 illustrates the project team structure which includes the Project Sponsor (Dr. Lu Zhang), the Project Manager (PM), and the other four members of the team. Due to a limited number of team members, some individuals are responsible for more than one role.

Project Manager (PM) – Swetha Yarra. The PM coordinates all activities of project team members, tracks, and monitors schedules, and progress against milestones, facilitates communication between team members, and works as a point of contact between the team and the sponsor. The PM does not necessarily need to be an expert in all roles, but the PM should know enough about each role to be able to effectively communicate with all team members and the sponsor.

Key relationships: All team members

· Key deliverables: Project proposal, ongoing progress reports, and general communication

Web Content Specialist & Database Administrator – Christopher Millard. The web content specialist is in charge of organizing, preparing, and loading website content. The web content specialist should have a basic understanding of HTML or XML, and a strong familiarity with site content and the general business or organization behind the website. The web content specialist should also have strong copy writing and editing skills. Web content specialists may also work with media files such as audio, video or interactive (Flash), and therefore may need those skills or may work with another media specialist outside the core web team to develop rich media content.

The Database administrator is responsible for building the database using Caspio web application and ensuring that the site and database are working together. The Database Administrator is also responsible for establishing relations between the entities.

Key relationships: User Experience (UX) designer, User Interface (UI) designer, Information Architect (IA), Quality Assurance (QA) Tester, and PM

· Key deliverables: Web contents and the database.

Information Architect (IA) – Hau Le. The IA is the chief planner of the website. The IA collects and documents requirements, including key objectives, functional requirements, and content requirements. The IA works closely with the UX designer and the project manager.

· Key relationships: UX designer, QA tester, and PM

· Key deliverables: Site map and requirements documentation.

User Experience (UX) & User Interface (UI) Designer –Emery Bullock. The UX designer uses the defined functional and content requirements for the site to formulate a set of page layouts designs and flowcharts describing how users will interact with the site. The UX designer works closely with an IA in developing a general strategic plan for building the website, and with the project manager to keep the project on target.

The UI designer (also called a web designer) is concerned with the visual presentation of the website. The UI designer may work with other graphic or print designers to synchronize the website’s appearance with related materials, or if needed, develop from scratch a visual identity, including logos, fonts, and color palettes. The UI designer then takes these elements, along with the page layouts designs, and develops a set of web page designs with full visual treatments. The UI designer may then turn these designs into web page templates using HTML and CSS, or may manage this task with the web developer.

Key relationships: IA, web developer, QA tester, and PM

· Key deliverables: Page layouts designs and flowcharts, web page designs, and web page templates (HTML/CSS)

Web Administrator & Quality Assurance (QA) Tester – Hector Roman. The web administrator is responsible for managing web environment design, deployment, development, and maintenance activities. The web administrator collaborates with development teams to discuss, analyze, or resolve usability issues. The web administrator tracks, compiles, and analyzes website usage data. The web administrator also documents application and website change or change procedures and develops or does procedures for web site revision. The web administrator’s duties also include testing new software packages for use in web operations or other applications and setting up or maintaining monitor tools on web servers or web sites. Moreover, web administrator tests the backup or recovery plans regularly and resolves any problems.

The QA tester ensures that the website functions as intended. The QA tester works with the IA and UX designer to identify a set of tests to be performed once the site is complete, to determine whether the site does what it is intended to do, and that it is free from bugs or other defects. When development and content preparation are complete, the QA tester will direct any rounds of testing, gathering feedback to deliver to the web developer for troubleshooting. This process will be repeated as necessary until the site is ready for launch.

Key relationships: web developer, IA, UX designer, and PM

· Key deliverables: fully functioning and well-maintained website, test cases, test process coordination, and feedback documentation for web developer

Functional Requirements & Requirements Traceability Matrix

1.0 Admin Setup

1.1 Create Yahoo email account

1.2 Create Wix Account

1.3 Create Caspio account

2.0 Design

2.1 Must have a Logo

2.2 Must have the title International Students San Diego

2.3 Must have Tabs that contain: Home, Housing, Universities, Recreation, Textbooks, Contact Us

2.4 Background must be standardized for all pages.

3.0 Login

3.1 When clicking on ‘Login/Setup’ must popup registration window.

3.2 Popup window for Signup must contain: Email, Password, Retype Password.

3.3 User must be able close the Sign-Up Pop Up window by clicking cancel or “X”.

3.4 Has to have a forgot password link

4.0 Technical and Usability

4.1 User can see public blog posts

4.2 Users can comment on Public Blog Posts

4.4 Cross-browser/platform support (IE, Firefox, Chrome, Safari – PC and Mac)

4.5 Mobile accessibility for IOS and Android

4.6 The site will fully function in major browsers:

· Safari

· IE

· Google Chrome

· Mozilla

Figure 3: Requirements Traceability Matrix

Nonfunctional Requirements

SEO

Search Engine Optimization (SEO) is the process of getting traffic, improving the visibility of a website or a web page in a web search engine's unpaid “natural” results. The project web pages should be decently optimized for SEO by having good HTML-structure. For this project, the team decides to use Wix. Wix sites are search engine friendly. Wix guarantee that the entire site content can be crawled and indexed by search engines (e.g. Google and Bing). Noted from Wix that after publishing, it can take 1-3 months for the site to appear in search engine results.

Getting a high ranking in search engine results depends on the work put into optimizing the site. To increase the chances of getting a higher ranking in search engines, the team should improve the site's content by optimizing the site's text, add Alt-Text to images, and update the page SEO settings (Meta Tags). The project team can also take advantage of social media by linking the site to social pages and adding a blog to the site. It is important to confirm that the team has set the site to be found by search engines. Once the team has followed the steps described above, the team needs to submit the site map directly to Google (Wix, 2016).

Wix also provides a web application called SEO Wizard. SEO Wizard offers a process-by-process guide to improving the site's Search Engine Optimization (SEO). This back-office App is a simple way to get the site discovered by all the major search engines. According to Wix (2016), with over 250 million sites on the web, this app will allow search for engines like Google, Yahoo, and Bing to find our site. It helps attract more traffic and makes it easy for current and potential users to find our site.

Furthermore, generating great content is arguably the most important thing that the project team can be doing to improve the search engine results. That said, by doing a few technical things right, it is a lot easier to achieve results. The easiest way to get these things right is to use a Content Management System (CMS) that takes care of the technical aspects. Here are the minimum features which the project team should be considered when using a CMS tool to edit each page: Title tag, meta-description, URL, semantic headlines, alt-text on images, and ability to add analytic tools.

Maintainability

A website needs to be maintained as well as developed. Designers of the website must consider how easy the site will be to add onto and to maintain during its lifetime (Locke, 2015). A maintainable system is understandable and modifiable. This means it is easy and simple to add new functions and features.

Ease of maintaining could mean several things:

· Our Website is maintained through our third-party service and in accordance with our Service Level Agreements.

· The database will be stored online through using a third-party service (www.Casipo.com). Maintainability of the service will be kept through our SLA.

In general, a maintainable site is one that can be quick, reliably updated with minimal downtime as possible, with lots of fallback protection if something goes wrong. Below is the list of actions to keep in mind when developing a maintainable site:

· Determine if the company has the resources to keep the information on the proposed website current and accurate

· Ensure that the site is functioning properly

· Maintain links within the website

· Respond to inquiries about the website and content

· Create and maintain the content for the website

· Ensure that all website contents comply with copyright laws

· Determine how often the content will be changed and updated. Date sensitive materials will require more attention. Official Web sites must also display page update dates at the bottom of every page.

Security

Users want the system to be secure so that they feel confident using it. However, security is not visible as-is and need to be clearly defined in the non functional requirements section. Security requirements are in a system to ensure unauthorized access to the system, and its data are not allowed, safeguard the integrity of the system from accidental or malicious damage. General security of our website will be the responsibility of our third-party service provided and is outlined in our Service Level Agreement (SLA).

Project Management

Project management is the art of adequately balancing communication, knowledge, skills, risk, technologies, tools, and techniques in the hopes of delivering a project as agreed upon or as expected. Project management must also account for competing demands, including the project’s goals as articulated through scope, almost certain time constraints, planned and unplanned financial costs, and quality –despite its measurement. While project management is an art that must adjust to constraints, project planning is, comparatively speaking, black and white. Known as the “quadruple constraint,” the project manager must choose which of the four constraints –scope, time, cost, and quality –are the most important and adjust accordingly (Schwalbe, 2006).

The nature of this Capstone necessitated an ordinary and disproportionate focus on scope and time. In short, the group chose to emphasize scope and time over cost and, to a degree, quality if it hoped to be relatively successful. The group managed the project’s scope through statements (e.g., vision and feasibility), by quasi-formal work breakdown structures via detailed tasking and through continuous requirements analysis. Time was managed primarily through milestones, Gantt charts, critical-path scheduling, and fast tracking. The latter technique shortens project schedules by doing activities in parallel that one would normally do in sequence (Schwalbe, 2006). Encouraging group members to design and write based on assumptions also used fast tracking.

Project planning and execution enabled quick adjustments to task slips. The project did not suffer from any deviation from its vision or feasibility. Early, strong planning may have actually strengthened it. All functional and non-functional requirements were initially identified from the outcome of the interviews with the sponsor as to the look, navigation, and output of the system. While there were also no deviations from the project’s project plan or work plan estimates, the project did slip during Milestone Three, when web interface development did not show needed progress by the end of the fifth week. Since interface design simplicity was central to the project’s scope, the goal by the end of Milestone Two was to have a pre-existing, template-driven site enabled for functional prototyping. These templates, save for minor adjustments, also served as the final layout.

Finally, while there were changes to areas of responsibility assigned to two group members at the conclusion of Milestone Two, work plan estimates remained accurate. Where some members fell short in level of effort, understanding, and quality of work required to realize these estimates, others were effective in filling subsequent gaps. This was also evident during system testing when test cases were not written as planned or produced when needed.

The project size stayed in line with provided timelines to include an absolute inability to miss specified delivery dates. Project alignment remained evident throughout its life. In short, SchoolTicketsOnline.com was delivered on time and the design exceeded stakeholder expectations. The Principal Developer and Quality Assurance Manager provide high quality and exhaustive contributions. See “Implementation,” p. 44 for the project’s history and implementation status at delivery. Also, see the project’s “Final Usability Report,” p. 51, which details the likelihood of the presence of minor system errors at delivery and recommended improvements based on end user testing.

Project Plan

Project planning is where it defines the core values of the project, which will be headed by the managers, no matter the industry, type of project, and different level of knowledge. At its core, a project plan defines the approach of the team and will have to manage the project according to the scope. Project management includes the competing demands which are enlisted through the scope, with certain constraints like planned or unplanned budget costs and the quality. The key major factors of project planning are the scope, time, cost, and quality (Schwalbe, 2006).

As a team, we choose to focus on scope and time over cost with a quality product. With a vision of developing a website for International students which provide information about the different universities in San Diego, local places to visit and also about the different textbook to enhance the skills of the courses they enroll which can be built through work breakdown structure with a detailed tasking through continuous requirement analysis. Time is the most important factor which needs to follow through every milestone and Gantt chart.

Project Work Breakdown Structure (WBS)

Running head: SDIS INFORMATIVE ONLINE RESOURCE CENTER

SDIS Informative Online Resource Center 32

1.1

1.2 Initiating & Planning

1.2.1 Initial Research

1.2.1.1 Business needs

1.2.1.2 Business environment

1.2.1.3 Targeted customers/users

1.2.2 Project Planning

1.2.2.1 Determine project scope

1.2.2.2 Construct timeline

1.2.2.3 Formulate team

1.2.2.4 Acquire & allocate budgets

1.2.3 Gathering Requirements

1.2.3.1 Functional requirements

1.2.3.2 Technical specifications

1.2.3.3 User requirements

1.2.3.4 Reporting requirements

1.2.3.5 Other requirements

1.3 Design

1.3.1 Front-End

1.3.1.1 Web design

1.3.1.2 Design web functions

1.3.2 Back-End

1.3.2.1 Design database & server

1.3.2.2 Plan applications

1.3.3 Interfaces

1.3.3.1 Design web/user Interface

1.3.3.2 Review interface Designs

1.3.3.3 Create interface Mock-ups

1.3.4 Reports

1.3.4.1 Design reports

1.3.4.2 Review report design

1.3.4.3 Obtain sign-off

1.4 Development

1.4.1 Front-End

1.4.1.1 Web development

1.4.1.2 Develop web functions

1.4.2 Back-End

1.4.2.1 Build database & server

1.4.2.2 Create applications

1.4.3 Interfaces

1.4.3.1 Build interface

1.4.3.2 Review interfaces

1.4.4 Reports

1.4.4.1 Report development progress

1.4.4.2 Review reports

1.4.4.3 Obtain sign-off

1.5 Testing & Documenting

1.5.1 Quality Assurance

1.5.1.1 Verify design and functionality

1.5.1.2 Perform integration test

1.5.1.3 Perform user acceptance test

1.5.1.4 Review test reports

1.5.1.5 Obtain sign-off

1.5.2 Establishing Support Knowledge Base

1.5.2.1 Create system documentation

1.5.2.2 Create training materials, tutorials, and manuals

1.5.2.3 Create troubleshooting guides

1.5.2.4 Review support knowledge base

1.5.2.5 Obtain sign-off

1.6 Implementation

1.6.1 Hardware & Software Acquirement

1.6.1.1 Determine hardware & software needs

1.6.1.2 Select appropriate hardware & software

1.6.1.3 Acquire hardware & software

1.6.2 Installation

1.6.2.1 Install hardware and software

1.6.2.2 Perform system test

1.6.2.3 Verify operation readiness

1.6.2.4 Obtain sign-off & deliver the system

1.7 Post-Implementation

1.7.1 System Monitoring & Control

1.7.1.1 Monitor performance and functionality

1.7.1.2 Verify log-issues

1.7.1.3 Perform scheduled maintenance/updates

1.7.2 Project Close-out

1.7.2.1 Obtain final project sign-off

1.7.2.2 Document & review

1.7.2.3 lessons learned

Figure 7: WBS

Project Schedule

Figure 8: Project Schedule

Risk Management

Our Risk Management Process includes the following five steps:

· Risk identification: The project team determines risks that could potentially prevent the team from achieving project’s objectives or satisfying project’s requirements. This step involves documenting and communicating the concerns during the team meeting.

· Risk assessment: The project team analyzes the probabilities and consequences of identified risk events. The results of this assessment are then used in the next step.

· Risk prioritization: The project team evaluates and ranks the analyzed risks in terms of their criticality or importance. This provides insights to the team on where resources may be needed to manage or mitigate a high probability/high impact risk.

· Risk treatment: The project team develops options and actions to improve opportunities and eliminate or decrease threats to an acceptable level.

· Risk monitoring & control: The project team track identified risks, identifies new risks, and evaluates risk process effectiveness throughout the course of risk management.

Figure 3: Risk Management Process

Risk Breakdown Structure

The entire reason of using risk management is to mitigate risk. The main purpose of risk management team is to protect organization assets without disturbing the objective of project. The risk breakdown structure will help to analyze the risk associated with the project. The risk mentioned here is majorly related with the project where complete team will be aware of the extent of the risks.

C:\Users\Sravan\Downloads\RBS (1).jpg

Fig: Risk Breakdown Structure

Risk Analysis

This is one of the most important phases of SDLC. For making a project success it is compulsory to ensure that it meets all the requirements and is fulfilled to a project’s success. If at any stage or even at the end of the project if it does not meet the requirement of the project will likely be considered as a failure, even if some derivative value is gained (Bandara et al, 2005). Analysts can create logical models, based on the requirements, which are gathered, the logical models like activity diagrams, entity relationship without disturbing the implementation details (Dennis et al, 2009) from which a risk analysis is conducted.

The major risk is associated with the key factors of the project that is the scope, time, cost, and quality (Galway, 2004). The highest affect risks of this project are:

1. Unexpected Software abnormalities: If the project team unable to identify or resolve problems of software it will cause these problems to escalate as the website develops further. This will cause a threat to the website’s completion will be delayed or even cause the website to undergo over problems. These problems will be raised because of human errors, hardware, and software incompatibility, or found in the development tools used by the project team.

2. Over Estimation of the project team’s abilities: This risk assessment will lead to the underestimation of project timeline, which indirectly has an impact on project’s performance.

3. Over-emphasis on low priority details: The basic requirements of the website development should be emphasized as Low Priority and High Priority. The changes in project requirements of the website development should be prioritized based on time and cost factors. As the high priority requirements are time consuming, very difficult to change the project plan in the last minute. A delay will happen if in case a low priority task is focused and a lot of time is spent on it then the project would be delayed.

4. Failure to meet the final deadline: The major mitigation to this risk is time management. Every phase in milestone needs to complete within time. According to schedule if any task is not completed then the risk associated with failing to meet the deadline will be lead to failure in completing the project.

5. Security issues: During initial planning and technical review the security concerns are addressed. They can be addressed through system testing. The database and web interfaces are sufficiently protected against the password, access to database and login details should be protected from the unauthorized users through high security.

Risk Assessment

Project manager can able to recognize the risks and should also have ability to control risks involved with project. Risk register or risk severity matrix will provide ability to analyze the severity of risk at any given point of time. For this project the risk is been divided into four major categories as

1. Technical

2. External

3. Organizational

4. Project Management.

5. Technical risk is again segregated into various risk factors. First, technical risk may poorly arise because of defined requirements or with complicate requirements. This type of risk may arise because of not defining the proper purpose of the project or also cause of not identifying proper checklist for the project. If the coordination of the team is not up to the point, the lead to the delivery of the final product would be of low quality. There might be chances of having technical disadvantages which may lead to sudden issues with the technical aspects and can lead to risk for the project. The technical disadvantages can be a bug issues or any change in the themes of the original website builder. If these issues arise from Wix then there might be chances of having poor technical support too.

6. The other major risk we can expect is through External factors. The external factors can be a third-party development application. As the project develops there might be a chance of involving third party by outsourcing for developing and web based application. There might be another reason for the external risk that is changed in laws and regulations which can be considered as uncontrolled risks. The competitive market is another factor of external risk, as there might be a huge chance of getting competitors as the technology is vast. The competition may be about economy or about applications or advancement in technical issues.

7. The risk can arise within the organization too. The reasons for organizational risk can be because of shortage of resources, funding problems, scheduling setback, or may be can also because of prioritizing errors. If the team coordination does not work properly within the organization, then there can be many issues related with the prioritization.

8. Project Management also will have some risks which can be because of lack of communication between the teammates, inaccurate cost estimation for the project plan. If the schedule estimation is not applicable if any changes occur in the budget plan, then the if the execution of the plan is not as per the plan then it will lead to the project failure. This happens because of ineffective planning. If the team is not having proper coordination, then it also will lead to disaster of the project. It can also happen because of faulty controlling of the team and project.

9. Once the risk assessment is identified and categorized by different sources from this the most important sources of risk can be differentiated based on the severity of the risk. Finally risk breakdown structure is identified with many risks and divided into major and minor severity of risks. In the RBS, risk concentration can be measured by the risk score based on the scale and size of each individual risk. The most common method to estimate is by chance (P) and Impact (I), which give the severity of the risk with the combination value of P & I.

Risk Reporting

It will help in rolling up all the information related to the risks involved in the project. This report will help in drilling down the information in detail. It will include the total number of risks in each higher-level RBS area.

Risk Severity Matrix & Urgency Response Plan

In general risk comes from hazards and harms. In order to project the project from this hazard or harm as team we planned some controlling measures which help in evaluation potential losses and taking action to reduce or eliminate the undesirable event. There is a scale for defining the severity and frequency of the risk by identifying the level of risk on predefined scale.

C:\Users\Sravan\Downloads\6.png

Figure

Risk response will help in developing the strategies for determining actions and also to reduce threats to the project objective. This will help in identifying risks and addressing them properly. If risk events are not solved through the techniques of avoidance, transference and mitigation then only technique to resolve issue is acceptance of the risk.

The risk severity matrix can be analyzed based on the graphical representation. If any risk fall in dark green color, then the risk is very low which can be considered as negligible likewise if the risk fall in light green color then risk is low. Yellow represents moderate risks while red and dark red gives indication of high risk factor.

C:\Users\Sravan\Downloads\5.png

Figure

This diagram represents which risks factor need to be resolved immediately. From the Risk Severity Matrix, the factors which fall into their zones will be segregated here and can be planned accordingly and implemented to take an action. As mentioned in the previous diagram the risk which falls into green color is not the urgent one to get resolved. In fact, they can be ignored while the risk which falls into the red zone is urgent and important which are supposed to be immediately, while the risk which falls into yellow zone is important but not urgent, which can be considered into plan to do list. The risk which falls into orange zone is very delegate they are urgent to get resolve but not important. So, based on the above diagram we can resolve the risk easily based on the factor how they affect the project.

Contingency Plan

Any problem occurs outside the range of normal operation which will adversely affect an organization’s ability to operate is a contingency plan. It is a plan of being prepared as an integral part of regular operation planning. For an unusual even it is a blueprint for how to deal and how to implement the plan. Regardless, of how big is the organization or how small every firm should have a contingency plan. The major role of contingency plan is to protect resources, identifies key staff and reduces the customer inconveniences, assigning specific responsibilities to the staff when needed for recover.

Responsibilities of Contingency Planning

In our project as we our major focus is on developing a website for International Students in San Diego, the contingency plan includes funding on proper time for development of website, test and maintaining the website. Project major will take the responsibility of operating the contingency plan when needed. It is Project manager responsibility to communicate with all the teammates and to train them on the plan and their responsibilities. We regularly test the plan using mock situations to identify problems and will see for any improvement and update the plan to reflect changes in the project.

Contingency Planning and Risk Identification

Developing contingency plan prepares the organization to respond when a high risk occurs. While addressing risk, we should consider both countermeasures and contingencies (Martin Webster). Counter measures include:

1: Prevention

2: Reduction

3: Transference

Risk analysis effectively starts with the identification of risks and its assessment of different potentials, which may harm the project for further operations. The contingency chart will describe the risks and help to address the risks, which are identified in the project. In the Risk assessment matrix risks are placed on the matrix based on two criteria:

· Likelihood: It will define the probability of risks.

· Consequences: This will show the severity of the impact of risk.

Problem Analysis

For the risk factors discussed above they can be analyzed with a positive scope. If the Bugs are identified them the quality assurance team will look into the issue and the senior programmer will fix the problem before the completion of the sprint, as the development team will report to the quality assurance team prior to the task completion day. Hence this planning will help to resolve the issue and have sufficient time to overcome the problem.

For the over- emphasis on low priority details is the responsibility of the project team to adopt the features driven approach in developing the website as the requirements of the project and do analysis and discuss with the team in every sprint meeting. The project team does the designing of the web page and develops the backend technologies in parallel

Another factor of problem analysis is the environment of the organization and the team members working (Schwalbe, 2006). It can be a system backup recovery plan; even the system testing in concern with the performance should be stimulated in a live environment.

Website Design

Website Mockups

Website Use Cases

Sign-Up

Password Reset

Database Design

Data Flow Diagrams

ER Diagram

Figure 4: ERD

Database Tables

Quality Assurance

Test Plan Process

The test plan process is segregated into (2) phases. The first phase exclusively involves the internationalstudentSD.com administrators. The administrators are tasked with the responsibility of testing all features applicable in administering the internationalstudentSD.com website, and database. Supplementary, the administrators will conduct thorough usability and functionally the user tests before beginning testing with user subjects. The second phase incorporates the utilization of a handpicked user group, comprised with users of various experience levels, to perform usability and functionality testing. Ultimately, the goal is to conduct (2) rounds of usability and functionality testing before launching the website and going live with internationalstudentSD.com. The intricacies of the administrator and user usability and functionality testing are addressed later in the quality assurance plan.

A synopsis of the test plan process is:

· Administrator testing of the WIX website account features.

· Administrator testing of the GUI based WIX website.

· Administrator testing of the WIX website external elements (Yahoo email account and external website links).

· Administrator testing of the support database.

· Administrator usability and functionality testing.

· User usability and functionality testing (testing subjects).

Error Checking

( Figure 5 : Error Checking Process )

After our website (www.sdishub.com) website has been created. Error checking of the website is important to ensure the website is operating successfully. There is myriad of services which are capable of checking your website for errors and finding ways of improving websites on the Internet. Some the common mistakes web developers fail to ensure when testing a website for errors are:

HTML Validation Errors- Do the website contain hidden errors? Although you can’t see them, the search engine can detect the error, and they don’t like errors on your websites. Errors such as HTML validation can hurt your search engine ranking or make it so potential visitors can’t see your site properly.

Broken Links- Broken links are unprofessional. All website sites should be tested by a website checker to ensure the pages lead to live web pages.

Meta Tag Content- Adding Meta tags can help search engines and visitors understand your site. Meta tags make also persuade users to click on your link in the search engine result. For example, Google shows your website title and description using Meta tags.

Web Page Size- if internationstudentSD.com does not load quickly, we risk losing customers. Error checking testing shows the size of your home page.

Technical Control Process

A well define website content production process is a good start. However, without a clear understanding of who is responsible for getting the process done is imperative.

Reviewing the web content may fall into:

· Subject Matter Experts

· Senior Editor

· Copywriter

· Marketing Manager

These tasks can be split across several roles. The subject experts may be asked to check if the content is accurate. The Senior Editor may check the website to ensure the content www.sdishub.com is well written, consistent with the rest of the website content.

Change Management Process

The Change Management Plan documents and tacks the necessary information required to effectively managing project change from project inception to delivery. The Change Management Plan is created during the Planning Phase of the project. Its intended audience is the project manager, project team, project sponsor and any senior leaders whose support is needed to carry out the plan. A detailed Change Management Plan can be seen in Appendix B.

The Change Management process establishes an orderly and effective procedure for tracking the submission, coordination, review, evaluation, categorization, and approval for release of all changes to the project’s baselines.

Step

Description

Generate CR

A submitter completes a CR Form and sends the completed form to the Change Manager

Log CR Status

The Change Manager enters the CR into the CR Log. The CR’s status is updated throughout the CR process as needed.

Evaluate CR

Project personnel review the CR and provide an estimated level of effort to process, and develop a proposed solution for the suggested change

Authorize

Approval to move forward with incorporating the suggested change into the project/product

Implement

If approved, make the necessary adjustments to carry out the requested change and communicate CR status to the submitter and other stakeholders. This step also includes testing and acceptance

Figure 6: Change Process

Website Test Plan

Testing Guidelines

The internationalstudentSD.com Quality Assurance (QA) Tester, under the direct supervision of the Project Manager (PM), is responsible for creating testing guidelines and collaborating with the User Experience (UX) and User Interface (UI) Designer to execute the quality assurance plan. In addition, the QA Tester is responsible for creating all testing documentation pertaining to the website, database, and external accounts, while recording user feedback on the administrator and user testing phases. In the case of this project, instituting appropriate testing procedures, coupled with copious documentation, is imperative. The QA Tester and UX/UI Designer will work hand-in-hand to develop reliable testing guidelines that must be approved by the PM prior to the initiation of testing.

The following is an outline of the testing guidelines:

· The QA Tester and UX/UI Designer will be on-hand to conduct the entire testing process of the website.

· The QA Tester and UX/UI Designer will meet regularly with the PM to provide updated testing statuses.

· Testing will be conducted in the order of website, external elements, database, and user usability and functionality testing.

· The QA Tester and UX/UI will not proceed from one area of the project to the next until the respective area being tested is complete.

· The QA Tester will guide the entire testing process while simultaneously recording findings and compiling documentation.

· The UX/UI Designer will assist the administrators and users with maneuvering through the website while answering any applicable questions.

· The same rule applies to the Server Administrator when testing the external elements and database.

· The QA Tester will use the testing documentation to provide a technical review and recommendations on change control processes.

Browser Performance Testing Missing

Usability Testing Incomplete

The project team performed this technique to properly evaluate our finished product by testing it with potential website users. We could measure how well our finished product will be received by the general public. The Usability Testing Survey focused on measuring the capacity of the product (website) to meet its intended purpose. This type of testing also measured the ease of use of our finished product by those who will be using the website.

It was important that our website is easy for customers to use and navigate with simplicity. The intent of this survey was to identify any potential problems that might have missed during the development phase. The team decided to survey a total of five people to ensure the response accuracy of the survey.

Please see Appendix A for sample of the survey questions for web usability testing.

[Add table of survey results]

[Add suggestions]

Following the completion of the Usability Surveys we complied the data into our Usability Report. This data and the completed report aided our team in fine-tuning elements of our final product.

Functionality Testing Missing

Project Implementation

Website Recovery Plan Missing

Project Completion

Lessons Learned Missing

Project Conclusion Missing

Appendices

Appendix A: Website Usability Testing Survey Questions

Tester:

Consider each statement and select your agreement with each one.

1. It is easy to navigate through this web site.

· Strongly Agree

· Agree

· Neutral

· Disagree

· Strongly Disagree

2. It is easy to find what I want on this web site.

· Strongly Agree

· Agree

· Neutral

· Disagree

· Strongly Disagree

3. This web site loads too slowly.

· Strongly Agree

· Agree

· Neutral

· Disagree

· Strongly Disagree

4. The graphics on this web site are pleasing.

Strongly Agree

· Agree

· Neutral

· Disagree

· Strongly Disagree

5. It is easy to use this site upon my first visit.

· Strongly Agree

· Agree

· Neutral

· Disagree

· Strongly Disagree

6. Clicking on links takes me to what I expect.

· Strongly Agree

· Agree

· Neutral

· Disagree

· Strongly Disagree

7. The organization of information on the system screens is clear.

· Strongly Agree

· Agree

· Neutral

· Disagree

· Strongly Disagree

Additional Comments/Suggestions:

Appendix B: Detailed Change Management Plan

Change Request Form and Change Management Log

Element

Description

Date

The date the CR was created

CR#

Assigned by the Change Manager

Title

A brief description of the change request

Description

Description of the desired change, the impact, or benefits of a change should also be described

Submitter

Name of the person completing the CR Form and who can answer questions regarding the suggested change

Phone

Phone number of the submitter

E-Mail

Email of the submitter

Product

The product that the suggested change is for

Version

The product version that the suggested change is for

Priority

A code that provides a recommended categorization of the urgency of the requested change (High, Medium, Low)

Evaluating and Authorizing Change Requests

Change requests are evaluated using the following priority criteria:

Priority

Description

High

Is necessary to meet requirements and will change the close date

Medium

Is necessary to meet requirements and will properly change the close date

Low

Little impact on the outcome of the project and provides business value

Change requests are evaluated and assigned one or more of the following change types:

Type

Description

Scope

Change affecting scope

Time

Change affecting time

Duration

Change affecting duration

Cost

Change affecting cost

Resources

Change affecting resources

Deliverables

Change affecting deliverables

Product

Change affecting product

Processes

Change affecting process

Quality

Change affecting quality

Change requests are evaluated and assigned one of the following status types:

Status

Description

Open

Entered/Open but not yet approved or assigned

Work in Progress

CR approved, assigned, and work is progressing

In Review

CR work is completed and in final review prior to testing

Testing

CR work has been reviewed and is being tested

Closed

CR work is complete, has passed all tests, and updates have been released.

Change Control Board

The Change Control Board will be made up of all team member and will meet when a CR is submitted. The project manager will have final say in all CR request.

Role

Name

Contact

Description

[Insert Role]

[Insert Name]

[Insert Contact #]

[Insert Role Description]

Version Control

All project documents changes need to be tracked. Our project team has implemented a Version Control System. There will only be one working document at any one time and will be stored in a single location. All changes will be recorded using the Version History table located at the beginning of every document.

Version control history table

Version #

Implemented

By

Revision

Date

Approved

By

Approval

Date

Reason

1.0

<Author name>

<mm/dd/yy>

<name>

<mm/dd/yy>

<reason>

Change Request Form

Change Request Form

SUBMITTER - GENERAL INFORMATION

CR#

Submitter Name

Brief Description of Request

Date Submitted

   

Date Required

Priority

|_| Low

|_| Medium

|_| High

|_| Mandatory

Reason for Change

Other Artifacts Impacted

Assumptions and Notes

Attachments or References

|_| Yes

|_| No

Link:

INITIAL ANALYSIS

Hour Impact

Duration Impact

Schedule Impact

Comments

Recommendations

CHANGE CONTROL BOARD – DECISION

Decision

|_| Approved

|_| Approved w/Conditions

|_| Rejected

|_| More Info

Decision Date

Decision Explanation

Conditions

Appendix C: Project Meeting

Project Meeting 1

Meeting/Project Name:

Project Kickoff & M1 – SDIS

Date of Meeting: (MM/DD/YYYY)

08/29/2016

Time:

5:30 PM

Prepared by:

Hau Le

Location:

NU Spectrum Campus

1. Meeting Objective

Brainstorming Ideas, Project Selection & Milestone 1 Discussion

2. Attendance at Meeting

Name

Role/Position

E-mail

Phone

Swetha Yarra

Project Manager (PM)

[email protected]

Hau Le

Information Architect (IA)

[email protected]

Christopher Millard

Web Content Specialist & Database Administrator

[email protected]

Emery Bullock

User Experience (UX) & User Interface (UI) Designer

[email protected]

Hector Roman

Web Administrator & Quality Assurance (QA) Tester

[email protected]

Brainstroming Ideas & Project Selection

All Team Members

5:30 – 6:30 PM

Milestone 1 Discussion

All Team Members

6:30 – 7:30 PM

4. Action Items

Action

Owner

Due Date

Document Executive Summary,Project Vision, Team Structure & Responsibilites

Hau Le

09/07

Document Overview Statement (Problem, Solution, Stakeholders, & Benefits)

Emery Bullock

09/07

Document Project Feasibility (SWOT Analysis)

Christopher Millard

09/07

Document Project Management (Project Plan, Risk & Problem Analysis)

Swetha Yarra

09/07

Create Use Case Diagrams & Descriptions

Hector Roman

09/07

5. Next Meeting (if applicable)

Date: (MM/DD/YYYY)

09/07/2016

Time:

5:30 PM

Location:

NU Spectrum Campus

Objective:

Milestone 1 Review & Milestone 2 Discussion

Project Meeting 2

Meeting/Project Name:

M1 Review & M2 Discussion - SDIS

Date of Meeting: (MM/DD/YYYY)

09/07/2016

Time:

5:30 PM

Prepared by:

Hau Le

Location:

NU Spectrum Campus

1. Meeting Objective

Milestone 1 Review, Presentation Preparation, & Milestone 2 Discussion

2. Attendance at Meeting

Name

Role/Position

E-mail

Phone

Swetha Yarra

Project Manager (PM)

[email protected]

Hau Le

Information Architect (IA)

[email protected]

Christopher Millard

Web Content Specialist & Database Administrator

[email protected]

Emery Bullock

User Experience (UX) & User Interface (UI) Designer

[email protected]

Hector Roman

Web Administrator & Quality Assurance (QA) Tester

[email protected]

Milestone 1 Review

All Team Members

5:30 – 6:00 PM

Presentation Preparation

All Team Members

6:00 – 6:30 PM

Milestone 2 Discussion

All Team Members

6:30 – 7:30 PM

4. Action Items

Action

Owner

Due Date

Create Project Proposal Presentation

Project Team

09/12

Create Website Mockups

Hector Roman

09/12

Document Functional Requirements & Requirements Traceability Matrix

Emery Bullock

09/21

Document Project Scope, Non-functional Requirements, WBS, & Project Gantt Chart

Hau Le

09/21

Create ER Diagram & Database Tables

Christopher Millard

09/21

Document Detailed Project Implementation

Swetha Yarra

09/21

Document Quality Assurance

Hector Roman & Emery Bullock

09/21

5. Next Meeting (if applicable)

Date: (MM/DD/YYYY)

09/21/2016

Time:

5:30 PM

Location:

NU Spectrum Campus

Objective:

Milestone 2 Review & 3 Discussion

Project Meeting 3

Meeting/Project Name:

M2 Review & M3 Discussion - SDIS

Date of Meeting: (MM/DD/YYYY)

09/21/2016

Time:

5:30 PM

Prepared by:

Hau Le

Location:

NU Spectrum Campus

1. Meeting Objective

Milestone 2 Review & Milestone 3 Discussion

2. Attendance at Meeting

Name

Role/Position

E-mail

Phone

Swetha Yarra

Project Manager (PM)

[email protected]

Hau Le

Information Architect (IA)

[email protected]

Christopher Millard

Web Content Specialist & Database Administrator

[email protected]

Emery Bullock

User Experience (UX) & User Interface (UI) Designer

[email protected]

Hector Roman

Web Administrator & Quality Assurance (QA) Tester

[email protected]

Milestone 2 Review

All Team Members

5:30 – 6:00 PM

Milestone 3 Discussion

All Team Members

6:00 – 7:30 PM

4. Action Items

Action

Owner

Due Date

Edit Project Paper

Team

10/10

Revise Functional Requirements

Team

10/10

Document Test Plan

Team

10/10

Risk Management Process

Hau Le & Swetha Yarra

10/10

Quality Assurance Process

Christopher Millard, Emery Bullock, & Hector Roman

10/10

5. Next Meeting (if applicable)

Date: (MM/DD/YYYY)

10/10/2016

Time:

5:30 PM

Location:

NU Spectrum Campus

Objective:

Milestone 3 Review & Milestone 4 Discussion

Project Meeting 4

Meeting/Project Name:

M3 Review & M4 Discussion – SDIS

Date of Meeting: (MM/DD/YYYY)

10/10/2016

Time:

5:30 PM

Prepared by:

Hau Le

Location:

NU Spectrum Campus

1. Meeting Objective

Milestone 3 Review & Milestone 4 Discussion

2. Attendance at Meeting

Name

Role/Position

E-mail

Phone

Swetha Yarra

Project Manager (PM)

[email protected]

Hau Le

Information Architect (IA)

[email protected]

Christopher Millard

Web Content Specialist & Database Administrator

[email protected]

Emery Bullock

User Experience (UX) & User Interface (UI) Designer

[email protected]

Hector Roman

Web Administrator & Quality Assurance (QA) Tester

[email protected]

Milestone 3 Review

All Team Members

5:30 – 6:00 PM

Milestone 4 Discussion

All Team Members

6:00 – 7:30 PM

4. Action Items

Action

Owner

Due Date

Edit Project Paper

Team

10/24

Document Intra Team Report

Christopher Millard

10/24

Document Inter Team Report

Christopher Millard

10/24

Conduct & Document Usability Testing

Hau Le

10/24

5. Next Meeting (if applicable)

Date: (MM/DD/YYYY)

10/24/2016

Time:

5:30 PM

Location:

NU Spectrum Campus

Objective:

Milestone 4 Review & Milestone 5 Discussion

Project Meeting 5

Meeting/Project Name:

M4 Review & M5 Discussion - SDIS

Date of Meeting: (MM/DD/YYYY)

10/24/2016

Time:

5:30 PM

Prepared by:

Hau Le

Location:

NU Spectrum Campus

1. Meeting Objective

Milestone 4 Review & Milestone 5 Discussion

2. Attendance at Meeting

Name

Role/Position

E-mail

Phone

Swetha Yarra

Project Manager (PM)

[email protected]

Hau Le

Information Architect (IA)

[email protected]

Christopher Millard

Web Content Specialist & Database Administrator

[email protected]

Emery Bullock

User Experience (UX) & User Interface (UI) Designer

[email protected]

Hector Roman

Web Administrator & Quality Assurance (QA) Tester

[email protected]

Milestone 4 Review

All Team Members

5:30 – 6:30 PM

Milestone 5 Discussion

All Team Members

6:30 – 7:30 PM

4. Action Items

Action

Owner

Due Date

Finalize Project Document

Team

Finalize Project Proposal Presentation

Team

5. Next Meeting (if applicable)

Date: (MM/DD/YYYY)

11/07/2016

Time:

5:30 PM

Location:

NU Spectrum Campus

Objective:

Milestone 5 Review & Lessons Learned Discussion

References

Identify

Treatment

Monitoring & Control

Assessemnt

Prioritization

Project Name:SDIShub.com

Project Manager Name:Swetha Yarra

Project Description:

ID

Assoc

ID

Funtional ReuirementsStatusTest Plan IDTest Plan Name

Requirements

Tested

Pass or Fail

Additional

Comments

0011.0

Admin Setup

0021.1

Create Yahoo Email Account

0031.2

Create Wix Account

0041.3

Create Caspio Account

0052.0

Design

0062.1

Must have a logo

0072.2

Must have the Title 'International Students San Diego

0082.3

Must have Tabs that contain: Home - Housing - Universities, Recreation - Textbooks, Contact Us

0092.4

Background must be standarized for all pages

0103.0

Login

0113.1

When clicking on 'Login/Setup' must popup registration window

0123.2

Popup Window for Singup must contan: Email, Password, ReType Password

0133.3

User must be able to 'Sign Up Pop Up' window by clicking cancel or "X"

0143.4

Has to have a forgot Password Link

0154.0

Technical and Usability

0164.1

Users can see Public Blog Posts

0174.2

Users can comment on Public Blog Posts

0184.3

Cross-Brower/Platform ( IE, Firefox, Chrome, Safari, Modzilla

0194.4

Mobile accessibility for Iphone and Android

0204.5

The site will fully function in major browsers

0214.5.1

Safari

0224.5.2

IE

0234.5.3

Google Chrome

0244.5.4

Modzilla

Information for International Students in the San Diego

REQUIREMENTS TRACEABILITY MATRIX

User

Administrator

WIX

Sign-up

Manage Users

Contacts Database

Create/Delete/

Modify Contacts

User

Administrator

WIX

Sign-up

Manage Users

Contacts Database

Create/Delete/ Modify Contacts

User

Administrator

WIX

Password Reset

Manage Accounts

Contacts Database

Create/Delete/

Modify Contacts

User

Administrator

WIX

Password Reset

Manage Accounts

Contacts Database

Create/Delete/ Modify Contacts

User

Login

Administrator

Web Page

Post Comment

Wix

Site Manager

Search Site

Click Links

Website

Review/Delete

Comments

Update Site Content

Add/Remove Links

Publish Changes

Staff/Admin

User/Customer

HAS

Incident

Partners/Affilates

PID

Password

Username

FNameLast Name

Phone/Cell

Email

Staff Username

FName

Phone/Cell

Last Name

Email

Solutions

Subject

Contact

Payout

Link/Code

Resolves

MessageUsername

Staff/Admin User/Customer HAS Incident Partners/Affilates PID Password Username FName Last Name Phone/Cell Email Staff Username FName Phone/Cell Last Name Email Solutions Subject Contact Payout Link/Code Resolves M1 M2 M3 M4 M1 M2 M3 M4 Message Username

Generate CR

Report Status

Log Updated Status

Implement CR

Authorize CR

Evaluate CR