Front | Back |
Analysis Phase of the SDLC
|
Analysis determines WHAT the business needs are. It includes activities designed to discover and document the features and functions the system must have.
|
Design Phase of the SDLC
|
Design takes the needs and determines HOW they will be met. Focus is on how to create a system that will provide the needed features and functions.
|
Main Activities of Design Phase
|
System Acquisition Strategy and Final Deliverable- System Specification
|
System Acquisition Strategy
|
Determining how the system will be implemented through make, buy, or outsource.
|
System Acquisition Strategy: Make
|
Building the system in house. Allows teams to have complete contol. Developers can be flexible and creative. High risks associated including costs, technical obstacles, and growing timeline.
|
System Acquisition Strategy: Buy
|
Buying a packaged software. More efficient to buy programs that have already been created, tested, and proven. Lack of customizing software. More reliable and can be affordable.
|
System Acquisition Strategy: Outsource
|
Hiring an external vendor, developer, or service to create the system. Requires the least amount of in-house resources. Benefits include more expertise on their part. Can reduce costs but have risks that include compromise of confidential information or lost control over future development.
|
Design strategy for System Acquisition Strategy: Make
|
Develop physical models of the new system that document how it will perform the functions. These physical models will represent the new system’s design before the system builders start constructing it.
|
Migration Plan
|
Specifies what activities will be performed and by whom when transition is made from old system to new.
|
Migration Plan: Preparing the business
|
|
Migration Plan: Preparing the technology
|
|
Migration Plan: Preparing the people
|
|
Six principles of User Interface Design
|
|
Layout
|
|
Content Awareness
|
|