user interface without the guts actually working Prototypes have inadequate or

User interface without the guts actually working

This preview shows page 254 - 264 out of 272 pages.

user interface without the guts actually working Prototypes have inadequate or missing documentation Users tend to embrace the prototype as a final system Should not eliminate or replace activities with a prototype
Image of page 254
DESIGN/DEVELOPMENT PHASE Computer-aided software engineering ( CASE ) tools are designed to support one or more activities of system development CASE tools sometimes contain the following tools: Project repository Graphics Prototyping Quality assurance Code generator Housekeepi ng
Image of page 255
DESIGN PHASE OUTPUT Design HW/SW strategy Architectural design Interface design Database and file design Program design Key deliverable: System Specification Building a house : hire an architect to draw blueprints for new house, hire builder who can build according to blueprints, plan specific features of house
Image of page 256
IMPLEMENTATION PHASE The purpose of the Implementation Phase is to construct the new or modified system and deliver it Develop programs Develop programs Install and test the new system Install and test the new system Train users Train users Convert to the new system Convert to the new system
Image of page 257
IMPLEMENTATION PHASE The program development life cycle follows these steps, note similarity to the overall SDLC : 1 1 Analyze the requirements Analyze the requirements 2 2 Design the solution Design the solution 3 3 Validate the design Validate the design 4 4 Implement the design Implement the design 5 5 Test the solution Test the solution 6 6 Document the solution Document the solution
Image of page 258
IMPLEMENTATION PHASE Various tests should be performed on the new system Unit test Unit test Verifies that each individual program or object works by itself Verifies that each individual program or object works by itself Systems test Systems test Verifies that all programs in an applicatio n work together properly Verifies that all programs in an applicatio n work together properly Integration test Integration test Verifies that an applicatio n works with other applicatio ns Verifies that an applicatio n works with other applicatio ns Acceptance test Acceptance test Checks the new system to ensure that it works with real-world data Checks the new system to ensure that it works with real-world data
Image of page 259
IMPLEMENTATION PHASE Training involves showing users exactly how they will use the new hardware and software in the system One-on-one sessions Classroom-style lectures Web-based training
Image of page 260
IMPLEMENTATION PHASE One or more of four Conversion Strategies can be used to change from the old system to the new system
Image of page 261
SECURITY PLAN A computer security plan should do the following: Identify all information assets of an organization Identify all information assets of an organization Identify all security risks that may cause an information asset loss Identify all security risks that may cause an information asset loss For each risk, identify the safeguards that exist to detect, prevent, and recover from a loss For each risk, identify the safeguards that exist to detect, prevent, and recover from a loss
Image of page 262
IMPLEMENTATION PHASE OUTPUT Construction Installation Testing Training plan
Image of page 263
Image of page 264

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture