Anda di halaman 1dari 17

Sheffield Hallam University

WEB APPLICATION DESIGN AND MODELLING (A-2011/2) WADAM

Project Plan Web Application Travel Itinerary Planning System

WEB APPLICATION DESIGN AND MODELLING (A-2011/2) WADAM

2012

Travel Itinerary Planning System

Distribution : Hallam Internet Systems Ltd

Document Version Control System - Google web docs Document Management Control - Google web docs
Version

v16

Document Authors Mr Adrian Ashley B.Sc (Hons) Mr. Mohamed Hagras Mr. Akilu Rilwan Muhammad Mr Zhao, Jian

Student ID 12030388 21046615 20049705

v18

Date 13/01/2012 13/01/2012 13/01/2012 13/01/2012

2|Page

WEB APPLICATION DESIGN AND MODELLING (A-2011/2) WADAM

2012

Travel Itinerary Planning System

Travel Itinerary Planning System


Project Plan

CONTENTS
1.0 INTRODUCTION AND OBJECTIVES
1.1 TRAVEL ITINERARY PLANNING SYSTEM WEB SITE OBJECTIVES 1.2 WEB SITE ACCESSIBILITY INTERVIEW 1.3 SYSTEM STATEMENT OF SCOPE 1.3.1 Functional Requirements 1.3.2 Non Functional Requirements 1.3.3 Future Enhancement 1.4 SYSTEM CONTEXT 1.5 CONSTRAINTS

2.0 PROJECT ESTIMATES


2.1 PROJECT RESOURCES 2.1.1 Minimal Hardware Requirements 2.1.2 Minimal Software Requirements

3.0 RISK MANAGEMENT


3.1 Scope and Intent 3.2 Risk Management Organisational Roles

4.0 PROJECT TEAM ORGANIZATION


4.1 TEAM STRUCTURE ROLES

5.0 DEVELOPMENT ENVIRONMENT


5.1 Project Development Environment

Glossary
APPENDIX A - Project Management APPENDIX B - MS Project 2010 APPENDIX C - QUALITY CONTROL

3|Page

WEB APPLICATION DESIGN AND MODELLING (A-2011/2) WADAM

2012

Travel Itinerary Planning System

1.0 INTRODUCTION AND OBJECTIVES


Assessment Task 1 As part of assessment on the module, you will design and implement a web application using objected oriented techniques, UML, Java and JSP's. You will be building an innovative application which will help people plan their travel itinerary. You will get further details about client requirements in next couple of weeks. You will be doing this assessment in a teams of 3-5 members. Please get yourself organised into teams and create your team in the Groups section on BB. Your first task is to produce a project plan for this project. You need to research what goes in a project plan and accordingly build your project plan for the web application you are going to build on the module. You need to submit your project plan using an online by 11:59 pm on 21st October. Hallam Internet Systems - Team members established 19/10/2011 Mr Adrian Ashley B.Sc (Hons) Student ID 12030388 Mr. Mohamed Hagras Mr. Akilu Rilwan Muhammad Student ID 21046615 Student ID 20049705

The approach will be to develop a plan of action comprising of tasks and managing our time with a Microsoft Project 2010, APPENDIX B - MS Project 2010

1.1 Travel Itinerary Planning System Web Site Objectives


The objective is to develop an innovative web application which will help people plan their travel itinerary the duration of the project is approximately 2.5 months, we will use MS project to schedule the tasks and generate a chart. APPENDIX B - MS Project 2010, and follow a project management system that uses the spiral model for software development APPENDIX A, Project Management, The project risks will be tracked and monitored along with journal submissions to blackboard at Sheffield Hallam University. All project members will experience all the roles and document their progress in the journals. Weekly project meetings have been booked into the university study rooms, one of the task will be for role change overs, and document journal updates and training support and task hand overs. The estimated milestones are recorded in the table below, Table 1 below

4|Page

WEB APPLICATION DESIGN AND MODELLING (A-2011/2) WADAM

2012

Travel Itinerary Planning System

Project plan Schedule


Web application Project
Travel Itinerary Planning System

Duration

Start date

End Date 13/01/2012 21/10/2011

Submission Milestones
Submission 1 (Project plan) - 5% Develop rapid prototype for interviewing users

2.5 Months 17/10/2011 Milestones Design Details


Design 1 Functional and Nonfunctional requirements Design 2 UML Use case diagrams for the web application Design 3 Classes and Object Design 4 Class diagrams
Web Site Software Development using Java 1 Web Site Software Development using Java 2 Design JSP Model Design

Submission 2 (Functional requirements) Submission 3 (Requirement Specification) Submission 4 (Further requirement specification)

4/11/2011 Est, 11/11/2011 Est, 18/11/2011 Est,

Submission 5 (Model Design)

2/12/2011 Est,

Submission 6 (Skeleton code)

Building 2 tier apps with Javabeans and JSPs Connecting JSP pages to database using JDBC

16/11/2011 Est,

Final team assignment submission

13/01/2012

Table 1, Project plan Schedule Estimate A prototype will be developed as means of developing the functional requirements and user interface this process will help develop the software specifications by interviewing the users this feedback will help during the development process and aid training for staff member. In order to manage the web applications development and increase a quality controls we will use spiral model for the software development, comprising of defined stages of the web applications development

5|Page

WEB APPLICATION DESIGN AND MODELLING (A-2011/2) WADAM

2012

Travel Itinerary Planning System 1.2 WEB SITE ACCESSIBILITY INTERVIEW


The objective of this feasibility interview was to investigate the steps need to make the planned web site more accessible to users. With the web application being a globally accessible system we anticipate that the web site must meet some basic design requirements so that it is more compatible with screen readers such as JAWS (www.freedomscientific.com 2011) I met with Mr Kyle Crossland who works at the Sheffield Royal Society for the Blind SRSB Thursday 20/10/2011 Subject of the meeting - Accessibility for the visually impaired user, he indicated that the organisation uses software called JAWS (www.freedomscientific.com 2011) The main point to keep in mind for the web based application is to avoid banners that refresh and precompiled animations and avoid using flash, and JAWS used information in Headings and Tags, JAWS do not use a mouse. In general for web sites, he recommended that if the font size could be increased and the default value saved in a cookies and the Z order, or the information has a good structure in terms of navigation. Conclusion - It should be feasible to increase the accessibility of the web site by including the above guidelines SRSB Sheffield Royal Society for the Blind 5 Mapplin Street Sheffield S1 4DT www.srsb.org.uk Tel: 0114 272 2757

6|Page

WEB APPLICATION DESIGN AND MODELLING (A-2011/2) WADAM

2012

Travel Itinerary Planning System 1.3 SYSTEM STATEMENT OF SCOPE


The scope of the systems is anticipated to follow the general model view controller ( MVC) comprising of Java, Java beans, Java Server Pages (JSP) and a Database would be used to implement the system, the diagram illustrate the system behaviour for a general system.

Figure 1, The Model-View-Control Architecture (Manual, 2005)

1.3.1 Functional Requirements


It has been determined that travel itinerary planning system will have the following functionalities; this list is subject to changes.

y y y y y y

Create a new user Store user's data according to United Kingdom data protection laws Login to the system and logout Create , edit and delete contents Keep track of user's prior searchers Accessibility all types of users (1.2 Web site accessibility Interview )

1.3.2 Non Functional Requirements


It has been determined that travel itinerary planning system will have the following nonfunctional requirements; this list is subject to changes.

y y y y y

Usability Security Database management system Response time Portability

7|Page

WEB APPLICATION DESIGN AND MODELLING (A-2011/2) WADAM

2012

Travel Itinerary Planning System

1.3.3 Future Enhancement


Future enhancements are subject to further user requirements gathering at a later date to enhance process it is anticipated that a prototype will be used as a means for further user requirements clarifications. This process is part of the management implementation for the software development life cycle which is part of the spiral model APPENDIX A, Project Management,

1.4 SYSTEM CONTEXT


The desired system context is indicated in the figure 2, below

Figure 2 System Context

1.5 CONSTRAINTS
The constraints of the 'Travel Itinerary planning system' have been highlighted during project meetings such;

y y y

Time Clarification of user requirements Technology

8|Page

WEB APPLICATION DESIGN AND MODELLING (A-2011/2) WADAM

2012

Travel Itinerary Planning System

2.0 PROJECT ESTIMATES


The project estimates were investigated excluding the financial terms, however other considerations were taken into account, such as staffing numbers for the project, this estimate would be more accurate with historical data from previous projects. This type of information would be useful for project planning, task allocation and budget allocation in the future.

2.1 PROJECT RESOURCES


The project resources need for the, Travel Itinerary Planning, web application was discussed and a number of technologies were tried and evaluated for their effectiveness of the resources. A prime important is the time is allocated for staff training and that systems are in place for the staff to acquire resources for the project, below is a non-limiting list of the resources needed for the project staff member are free to add to this list as the project progresses.
TABLE 2 Resources RESOURCES Time , Prototypes ,Java, JSP, Oracle Database Microsoft Office Products MS Project 2010 MS VISIO 2010 Source Safe Document Control such as Google Docs Documentation Standards Training Software coding Standards Training Time for training using the eclipse development environment Project Managements tools training and methods such as Spiral model , UML, SSADM REASON Staff training for the latest software versions and that the staff can make the most of the application and reduce the error, and increase quality Industry standard, well established, all staff has access Used for task project management Used for diagrams So the development is sources and versioned correctly and all staff has access to the web application developm ent code To keep the documents up to date and available for all staff members and assists in the project management and project journal So there is a common method of versioning and presenting the information and tracking So there is a common method of versioning and coding so the other staff member can follow the syntax or java code The Eclipse is the main development environment , it is important that all staff are confident with the development environment and are able to use and demonstrate the web project , So the staff are able to use and apply these managements tools so the web application is development with a higher quality and reliability and AVAILABLE Yes Yes Yes Yes Pending x Yes Yes Yes Yes

Yes

2.1.1 Minimal Hardware Requirements


The minimum hardware requirements have been ascertained from the Oracle corporation the following link http://www.java.com/en/download/help/sysreq.xml Web Hosting - Server Computer the system requirements are indicated in the above link Web Applications Development - PC Computer , the specification is dependent on the software requirements

2.1.2 Minimal Software Requirements


The minimum hardware requirements for the web application as follows; subject to changes Eclipse Development Environment Database , such as Oracle , SQL Server or My SQL Apache Server , a version compatible wither Java 6 Windows 7,XP or Linux OS Java SDK

9|Page

WEB APPLICATION DESIGN AND MODELLING (A-2011/2) WADAM

2012

Travel Itinerary Planning System

3.0 RISK MANAGEMENT


The risk management of the project was investigated and a number of risk factors were highlighted and steps to counter act the risks addressed, the team will continue to monitor and manage the risks during the web application development.

3.1 SCOPE AND INTENT


To reduce the risk of the scope of the project becoming to wide, this problem is also known as feature creep, this best described as after a project begins more features are added causing chaos

3.2 RISK MANAGEMENT ORGANISATIONAL ROLE


Training for the latest technologies so the staff members are updated with the latest software The risk or management of the risk or organisation roles of the project will be substantially reduced by the structure of the project. Risk of software compatibilities, Risk of organisational role such as staff not familiar with their job task, or responsibilities to, counteract this risk and the table below show the job task description, subject to changes and update with journal information. TABLE 3, Risk of Organisational Roles Risk Monitoring Project Manager
Mr. Mohamed Hagras Mr Adrian Ashley B.Sc (Hons) Mr. Akilu Rilwan Muhammad Mr Zhao, Jian

Journal Update

Communications Administrator

Documentations & Backup Administrator Staff Training Administrator

Responsibilities overall project tasks sequence and activity Providing staff needs Team Meeting attendance recording Update Project requirements Change management Process staff requests Document standards Coding standards
UML Maintenance

Maintaining staff training for the project Risk monitoring, Document control Build the Web Application to the specification Maintain coding standards Build test prototypes and document code Document reference material used Manager software changes Build the database to the specification Build test prototypes and document code Manager database changes
Testing the web applications Testing to the UML Design specifications

Software Developer

Database Developer

Testing & Feedback

10 | P a g e

WEB APPLICATION DESIGN AND MODELLING (A-2011/2) WADAM

2012

Travel Itinerary Planning System

4.0 PROJECT TEAM ORGANIZATION


The project team organisation was investigated in order to complete the web application with maximum contribution from all staff members.

4.1 TEAM STRUCTURE ROLES


The roles in the team structure are dynamically allocated in a weekly rotation bases so everybody has a chance to contribute and when they do this role they do a brief documentation so the next person who takes this role will carry on doing the work and all information will feed into the journals.

Work according to project paln and adjust it for future needs

Project Manager

Group Administration

Communications Administrator

Documentations & Backup Administrator

Staff Training Administrator

Project Implementation

Software Developer

Database Designing & Developing

Testing & Feedback

/ Mr. Akilu Rilwan Muhammad / Mr Zhao, Jian Mr Zhao, Jian Responsibilities overall project tasks sequence and activity be aware of staff needs and

THE ROLES Project managers - Mr. Mohamed Hagras / Mr Adrian Ashley B.Sc (Hons)

coordinate progress and follow the spiral model and MS Project task sequence - review the project status compares to the objectives Communications Administrator Mr Adrian Ashley ,Mr Zhao, Jian - Responsibility coordinate information for the project and document standards and coding standards and update project requirements for the new web application, Change management project , process staff requests Documentations & Backup Administrator Mr Zhao, Jian - Maintain documentation control and backups for the project in a document control system such as Google docs , and check software backups in a source safe system, such as MS Source safe Staff Training Administrator - Maintaining staff training , Risk monitoring, Document control Software Developer - Mr. Mohamed Hagras / Mr Adrian Ashley B.Sc (Hons) / Mr. Akilu Rilwan Muhammad Build the Web Application, Maintain coding standards; Build test prototypes and document code, Document reference material used, Training example s to the document control system. Manager software changes

11 | P a g e

WEB APPLICATION DESIGN AND MODELLING (A-2011/2) WADAM

2012

Travel Itinerary Planning System


Database Developer - - Mr. Mohamed Hagras / Mr Adrian Ashley B.Sc (Hons) / Mr. Akilu Rilwan Muhammad Build the database , Maintain database standards with documentation

Testing & Feedback - Mr. Mohamed Hagras / Mr Adrian Ashley B.Sc (Hons) / Mr. Akilu Rilwan Muhammad, Mr Zhao, Jian Testing GOOGLE Maps the web application and feedback the quality of the documentation compared to the standards

5.0 DEVELOPMENT ENVIRONMENT


To meet the prototype and training requirements all staff members should download and set up the development environment and run a small JSP web application from examples and document this training activity to document control.

5.1 Project Development Environment


In accordance to the blackboard instructions, the development environment can be set up as follows, Ref. Blackboard VLE Sheffield Hallam University

Installing the software at home

Please use the link below to download Eclipse

It's a zip file so you can just unzip the file and you will find an application file called Ecpilse.exe. Just double click on this file and it will run. There is no need to install this tool. In addition to this we will also be using a web server called Tomcat on the module, again you can download the server using On this page you will find 'Binary Distribution' under this heading you will find a number of files, please download the 'Windows Service Installer'. This is an exe file, once you download it just run the file, this will start the installation for the server.
http://tomcat.apache.org/download-60.cgi

12 | P a g e

WEB APPLICATION DESIGN AND MODELLING (A-2011/2) WADAM

2012

Travel Itinerary Planning System

The development environment can be downloaded from the link below also noted is capability for UML
http://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/ganymede/SR1/eclipse -jee-ganymede-SR1-win32.zip

13 | P a g e

WEB APPLICATION DESIGN AND MODELLING (A-2011/2) WADAM

2012

Travel Itinerary Planning System

14 | P a g e

WEB APPLICATION DESIGN AND MODELLING (A-2011/2) WADAM

2012

Travel Itinerary Planning System

Bibliography
Manual, A. D. F. C., 2005. Application Development Framework Case Manual. [Online] Available at: http://download.oracle.com/docs/cd/B25016_08/doc/dl/web/B19163_01/adfcase_intro.htm [Accessed 20 10 2011]. www.freedomscientific.com, 2011. FreedomScientific. [Online] Available at: http://www.freedomscientific.com/products/fs/jaws-product-page.asp [Accessed 20 10 2011].

Glossary
JSP Java Server Pages SQL Structured Query Language UML Unified Modelling Language

Further Reading
DOCUMENTS Quality Assurance Plan Configuration Management Plan Risk Management Plan Project Schedule

15 | P a g e

WEB APPLICATION DESIGN AND MODELLING (A-2011/2) WADAM

2012

Travel Itinerary Planning System

APPENDIX A, Project Management

Ref 3.The Spiral Model diagram from (Boehm 1987) http://www.ics.uci.edu/~wscacchi/Papers/SE-Encyc/Process-Models-SE-Encyc.pdf

16 | P a g e

WEB APPLICATION DESIGN AND MODELLING (A-2011/2) WADAM

2012

Travel Itinerary Planning System

APPENDIX B MS Project 2010


Usage inset a task and notes and allocates a time to evolve a project plan indicated by the Gantt chart

17 | P a g e

Anda mungkin juga menyukai