Building Information Systems - L20

Get Started. It's Free
or sign up with your email address
Rocket clouds
Building Information Systems - L20 by Mind Map: Building Information Systems - L20

1. Prototype System

1.1. Definition: A working model built to learn how a work system could operate - a version of the final system. A version that requires improvement and understanding of the flaws.

1.1.1. Prototype Development Phases First Phase - Initiation: Communication with users about vaguely written requirements. Second phase - Development: User assesses each version that is developed, giving feedback. Final version only when users are satisfied. Third phase - Implementation: Users test the system. Training requirements are unnecessary as users + developers are already involved in the process through testing (2nd phase). Fourth phase - Operation Maintanence: Developers must provide documentation on how to keep system running and train users. Also, system has to be updated accordingly to changes in end user environment (i.e. hardware/software)

1.2. Types: Throwaway (temp). Designed to be discarded. When final solution isn't known, a simplified system is made. Helps make decisions. Evolutionary: (permanent). Designed to be adapted for normal use. Suitable for when final design is known. Req: Designed with final IS in mind.

1.3. Advantage: Suitable when the problem isn't; fully known. Having prototype helps to understand strengths and weaknesses. Users also have a tangible IS to work with during development. Reduces skepticism as everyone is kept informed of development.

1.4. Disadvantage: Production of many versions is labour/time intensive + costly.

2. Application Packcage

2.1. Produced by software vendors like MS. Packages can be shrink-wrapped (i.e. Office 365 - whole suite premade) or bespoke systems tailored to client.

2.1.1. Development: Selection: Vendor may assist in selection of shrink-wrapped package or design if bespoke needed. Benchmarking: Using data we can run tests to evaluate product - helps to identify whether bespoke or premade system needed. Request for proposal: Functional specification translated into checklist of required features.

2.1.2. Implementation: Deciding how package will be set up and used. System documentation may have to be extended with a training manual.

2.1.3. Operation and maintenance: Vendors may produce new releases (upgrades), patches, and supply support with help desk. License agreements govern the use of the system with respect to number of sites, number of users etc.

2.2. Advantages:

3. End User Development

4. Traditional Life Cycle

4.1. Definition: Project divided into number of steps. Well defined deliverables to move from UR to final system.

4.2. Advantages: Best system when UR are known. Adherence to fixed deliverables. Easy to monitor and take correct actions early.

4.3. Disadvantages: Too much user interaction leads to frequent changes to spec.