My Profile
Active Members
TodayLast 7 Days
more...
Awards & Gifts
Online Exams
Fresher Jobs
Our fresher job section is exclusively for fresh graduates! Find jobs for freshers in major Indian
cities including Bangalore, Chennai, Hyderabad, Pune or Kochi
Resources
Find educational articles, blogs, discussion threads and other resources.
Colleges
Find details about any college in India or search for courses.
Paid Surveys
|
waterfall model
Posted Date: 19 May 2008 Resource Type: Articles/Knowledge Sharing Category: Computer & Technology
|
Posted By: sri phani kumari Member Level: Gold
Rating:  Points: 1
|
|
|
Introduction
The purpose of producing an Orange Lifecycle Standard for Waterfall is to try to inject an element of commonality across different development approaches, the output of which is the production of a standard minimum set of project documentation. Mandatory project documentation is show in red and is 'shadowed' on the schematic.
The decision regarding which development approach to adopt will have been made in the IT Project Definition Report.
The Project Manager should also have made an assessment of the requirements for usability testing >>>
Since usability techniques can be applied at any stage of the development lifecyle, herewith three examples of usability activities that can be carried out at the outset of a project >>>
The Waterfall Lifecycle
The Waterfall lifecycle has 6 separate stages All fit well within the 'Deliver' phase of the Orange Project Management Framework introduced by the IT Project Office.
The 6 stages are:-
Analyse Requirements
Prepare System Specification(s)
Develop Software
Prepare for System Testing
Perform System Testing
Prepare for Implementation
The Waterfall schematic is detailed below:-
Analyse Requirements
The aim of this stage is to scope the business functions to be supported by the proposed new system and should:-
identify classes of users and capturing their requirements in a succinct, complete and unambiguous form
provide a firm basis for technical development
identify any major risks associated with the project
provide revised IT estimate
refine the MS project plan produced in the IT Project Definition Report
identify UAT Test Cases
identify and request pakaging for any applications that will need to be installed on the Eden desktop. Consider applications that will be needed by the project (e.g. compilers, CASE tools) as well as applications that will be developed by the project. Remember Eden require at least 6 weeks notice. If your target customers are not on the Eden domain, your Eden contact will be able to advise.
consider infrastructure capacity implications
identify number and location of users
identify performance requirements
identify class of service (e.g. mission critical)
procure hardware if appropriate
usability
set usability objectives >>>>
produce UAT Test Cases for usability testing
organise test environment, especially if usability testing is required
Documentation Output: Business Requirements Specification
UAT Test Cases (also for usability testing if necessary)
Revised IT estimate
Request for Eden Packaging >>>
Request for Infrastructure Capacity >>>
Request for Test Enironment >>>
Prepare System Specification(s)
The key output from this stage is the production of the Functional Specification(s) which will specify the design that fulfils the BRS.
analysis of system requirements
the identification of detailed system requirements, depending on the level of complexity supplied by the BRS
Additional output from the Functional Specification should identify:-
hardware requirements
system test cases
user tasks (if users exist)
consider infrastructure capacity implications
confirm hardware environment
size application (hardware infrastructure required e.g. server, storage, networks)
usability evaluation methods
consider a card sorting exercise for domain names, labels and structure
hold usability walkthroughs
consider paper prototyping
consider Expert (or Heuristic) Evaluation
Click here for examples of usability evaluation methods >>>
Take into account relevant local standards when designing systems e.g. Eden Packaging >>>
Documentation Output: Functional Specification
System Requirements Specification (if appropriate)
Technical Design Document (if appropriate)
System Test Cases
Infrastructure Design Specification >>> (complicated requests) >>> (Fast Track)
Usability - a report or list of problems identified during the evaluation and recommendations for the next phase.
Develop Software
The purpose of this stage is to develop an application to satisfy the business requirements. Deliverables include:-
application code, tested on a unit basis
the application of component version control
the production of Software Maintenance Notes
Documentation Output:Software Maintenance Notes
Prepare for System Testing
Upon completion of Unit testing, system testing can commence. At this stage, the MS project plan should be refined and a revised IT estimate made. An Operational Specification should be produced outlining operational procedures necessary to run the system on a day-to-day basis. Consider some small-scale usability testing. For example, if a user task uses a single module of software application, a usability test can focus on this task alone.
Documentation Output: Test Plan
Operational Specification
Revised IT estimate
Updated MS Project Plan
Perform System Testing
Once System Test Plans are produced and System Configuration Control applied, system testing should be performed and signed off by the senior analyst concerned or the IT Manager. It should be possible to supply a realistic IT estimate at this point. Small-scale usability testing could be undertaken here (e.g. if a user task uses a single module of a software application, a usability test can focus on this task alone)
Documentation Output: Revised IT estimate
System Test Sign-Off
Prepare for Implementation
Prior to the handover of the application, the following matters should be considered:-
prepare Integration Test Plans (or handover to the Orange Integration Test Team)
if a need for new Live System Hardware was identified during the Prepare System Specification phase, install it (provision of hardware infrastructure initiated via Request for Capacity)
use the UAT test cases identified during the Analyse Requirements phase to prepare UAT Test Plans
complete user training and documentation
full-scale usability testing
follow-up usability testing after changes have been made
Click here for relevant examples of late Usability activities >>>
Documentation Outpu: User Documentation
(only if users are involved as there are some applications within Orange that do not have end users)
ITT Test Plans
UAT Test Plan
Usability - a record of user comments & actions. A report which includes
a problems list and recommendations for improvements to the system
|
Responses
|
| Author: sunilkumar 19 May 2008 | Member Level: Bronze Points : 2 | good article
| | Author: Raghav 19 May 2008 | Member Level: Gold Points : 2 | Very good article
|
|
|