PORTFOLIO

Software Management Portfolio



Software Management Portfolio

Part A: Define Software Prototyping, explaining its component stages

Development of a preliminary version of a software system in order to allow certain aspects of that system to be investigated. Often the primary purpose of a prototype is to get feedback from the intended users; the requirements specification for the system can then be updated to reflect this feedback, and so increase confidence in the final system. Additionally (or alternatively) a prototype can be utilised to investigate specific problem areas, or certain implications of alternative design or implementation decisions (Melissa Mcclendon, 2002).

The aim with a prototype is normally to get the required information as rapidly as likely and with the minimum investment of resources, and it is thus widespread to concentrate on certain aspects of the intended system and completely ignore others. A prototype may for example be developed with no concern for its efficiency or performance, and certain functions of the final system may be entirely omitted. It should however be very shrewd in those aspects expressly under investigation.

Software prototyping, mentions to the activity of creating prototypes of software applications, i.e., incomplete versions of the software program being developed. It is an activity that can happen in software development and is comparable to prototyping as renowned from other fields, for example mechanical engineering or manufacturing. A prototype typically simulates only a couple of aspects of the final solution, and may be completely distinct from the final product (Stephen, 2003).

Prototyping has several benefits: The software designer and implementer can get valuable feedback from the users early in the project. The client and the contractor can compare if the software made matches the software specification, as asserted by which the software program is built. It furthermore allows the software engineer some insight into the correctness of initial project estimates and if the deadlines and milestones suggested can be successfully met. The degree of completeness and the techniques utilised in the prototyping have been in development and debate since its proposal in the early 1970s (John, 2005).

Software Prototyping process

The process of software prototyping involves the following steps:

Identify basic requirements: Determine basic requirements encompassing the input and output information desired. Details, for example security, can typically be ignored.

Develop Initial Prototype: The initial prototype is developed that encompasses only user interfaces.

Review: The customers, encompassing end-users, examine the prototype and provide feedback on additions or changes.

Revise and Enhance the Prototype: Using the feedback both the specifications and the prototype can be improved. Negotiation about what is within the scope of the contract/product may be necessary. If changes are introduced then a repeat of steps #3 and #4 may be needed (John, 2005).

Dimensions of prototypes

Horizontal Prototype

A widespread term for a user interface prototype is the horizontal prototype. (Melissa Mcclendon, 2002) It provides a broad view of an whole system or subsystem, focusing on user interaction more than low-level system functionality, for example database access. Horizontal prototypes are helpful for:

Confirmation of user interface requirements and system scope

Demonstration version of the system to ...