There are two types of prototyping incremental or evolutionary and throwaway

There are two types of prototyping incremental or

This preview shows page 69 - 78 out of 120 pages.

There are two types of prototyping:incremental or evolutionary and throwaway.
Background image
Incremental and Iterative ApproachIn incremental development, the product isbuilt through successive versions that arerefined and expanded with each iterationThree concepts underlie the incrementalapproach:The Initialization StepThe Control ListThe Iteration Step
Background image
Throwaway ApproachIn the incremental approach,the initial prototype is revised and refinedrepeatedly until it becomes the final product.In the throwaway approach,the prototype is discarded after the stakeholdersin the development are confident that they havearrived at the correct specifications and thedevelopment on the “real” product can start.
Background image
Problems with PrototypingUnbalanced ArchitectureSince the main thrust of prototyping is towards the user interface, thedevelopers tend to include more and more functionality in the outer layers ofthe information system, creating a distorted architecture.The Illusion of CompletenessSince the clients might not understand why the developers insist that a lotmore is to be done, the prototype may successfully present the user interfacefor a complex functionality the feasibility of which is far from certain.Diminishing ChangeabilitySince prototyping can leave little trace of how the development evolved,modifying the application can resemble an archeological undertaking to piecetogether a lost civilization.Prototyping can result in too little documentation or, more importantly,too little modeling.
Background image
The Spiral ModelThe spiral model is a riskoriented lifecyclemodel that breaks a software project up intominiprojects.
Background image
Rapid Application Development (RAD)Rapid Application Development is selectingtechniques, methods, practices andprocedures that would result fasterdevelopment and shorter schedules.
Background image
Characteristics of RADRequirements PlanningAims at eliciting information and requirements from the senior people andverifying the goals.DesignThe design phase begins once thetoplevelrequirements of the system areidentified. To discover more detailed requirements, RAD relies on JointApplication Development (JAD) workshops.ImplementationOnce the users approve the preliminary design, a detailed design of thesystem is created and code is generated. Implementation phase is heavilydependent upon CASE tools.Enhancements and MaintenanceIn the framework of RAD, a software is never completed until it is retired.there is no significant difference between development and maintenance.(This position is in opposition to most SDLC methodologies.)
Background image
Agile MethodologiesAgile methodologies aim at being adaptiverather than predictive.
Background image
Extreme Programming (XP)A betterknown example of agile methods, andone of the earliest ones, is Extreme Programming(XP).
Background image
Image of page 78

You've reached the end of your free preview.

Want to read all 120 pages?

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture