Alternative Approaches to Development Prototyping A repetitive process in which analysts and users build a rudimentary version of an information system

em based on user feedback. Repeated cycle: build, use, evaluate Building a scaled-down working version of the system Advantages: Users are involved in design Captures requirements in concrete form

When to Use Prototyping? Users are unclear about their requirements -The system affects a relatively small number of users Designs are complex -Communication between users and analysts needs to be strengthened Rapid application development tools are available Pitfalls of Prototyping -Tendency to avoid creating formal systems requirement documentation -Prototypes may be indiosynchratic to the individual user and difficult to adapt for others -Prototypes are designed as standalone systems, so do not address data sharing and integration -Checks in SDC are bypassed, so issues like security, controls and standardization may be ignored Computer-Assisted Software Engineering (CASE) Tools Automated software tools used by systems analysts to develop information systems Can be used throughout SDLC

Product and tool integration is provided through a repository Enabling user to more easily manage larger, more complex projects and to seamlessly integrate data across various tools and products General types of CASE tools Diagramming tools

- represent graphically Computer display and report generators

- look and feel Analysis tools

- automatically check Repository

- integrated centralized database Documentation generators

- produce standard format Code generators

- automatic generation Joint Application Design (JAD) -It brings together business area people and IT professional in a workshop -Participants get together in a room to discuss the problem/project -Listen to everyone opinion -Save time and improve quality of the final product WHY JAD? People who actually do a job have the best understanding of the job People who trained in Information Technology have the best understanding of the possibilities of the technology

Rapid Application Development (RAD) -System developers and end users work together to develop system -Objective is to decrease the development time and expenses -Have four phase -Involving end-users in every phase

Participatory Design -Attempting to involve all stakeholders in design process -Help to ensure the product designed meets their needs and usable.

Agile Methodologies Focuses on Adaptive methodologies People instead of roles Self-adaptive development process