INSY 3305 EXAM 1 REVIEW ACTUAL UPDATED QUESTIONS AND CORRECT
ANSWERS
Systems Development Life Cycle - Four stages
- Planning, Analysis, Design, Implementation
- Executed sequentially, incrementally, iteratively or in some other pattern.
SDLC: The Planning Phase 1. Project Initiation
- Develop/ receive a system request
- Conduct a feasibility analysis
2. Project Management
- Develop a work plan
- Staff the project
- Monitor & control the project
Deliverable: Project Plan
SDLC: The Analysis Phase 1. Develop an analysis strategy
- Model the current system
- Formulate the new system
2. Gather the requirements
- Develop a system concept
- Create a business model to represent business data and business processes
3. Develop a system proposal
Deliverable: System proposal
,SDLC: The Design Phase 1. Develop a design strategy
2. Design architecture and interfaces
3. Develop databases and file specifications
4. Develop the program design to specify:
- What programs to write
- What each program will do
Deliverable: System specification
SDLC: The Implementation Phase 1. Construct the system
- Build it (write the programming code)
- Test it
2. Install system
- Train the users
3. Support the system (maintenance)
Implementation: New system and maintenance plan
SD Methodology: Structured Development - Waterfall development
- Parallel Development
SD Methodology: Rapid Application Development - Phased
- Prototyping
SD Methodology: Agile Development - Extreme programming
- SCRUM
Object-Oriented Systems Analysis and Design (OOSAD) - Attempts to balance data and process
- Utilizes the Unified Modeling Language (UML) and the Unified Process
- Characteristics: Use-case driven, Architecture Centric, Iterative and Incremental
Classes & Objects - A characteristic of an object-oriented system
- Object (instance): instantiation of a class
- Attributes: information that describes the class
- State: describes its values and relationships at a point in time
, Methods & Messages - A characteristic of an object oriented system
- Methods: behavior of a class
- Messages: information sent to an object to trigger a method (procedure call)
Encapsulation & Information Hiding - A characteristic of an object oriented system
- Encapsulation: combination of process and data
- Information hiding: functionality is hidden
Inheritance - A characteristic of an object oriented system
- General classes are created (super classes)
- Subclasses can inherit data and methods from a superclass
Polymorphism & Dynamic Binding - A characteristic of an object oriented system
- Polymorphism: the same message can have different meanings
- Dynamic binding: type of object is not determined until run time
Contrast with static binding
Use-Case Driven Define the behavior of a system, each focuses on one business process
Architecture Centric - Functional (external) view: focuses on the user's perspective
- Static (structural) view: focuses on attributes, methods, classes, and relationships
- Dynamic (behavioral) view: focuses on messages between classes and resulting
behaviors
Iterative & Incremental Undergoes continuous testing and refinement, the analyst understands the system
better over time
Benefits of Object-Oriented Systems Analysis and Design - Break a complex system into smaller, more manageable modules
- Work on modules individually
ANSWERS
Systems Development Life Cycle - Four stages
- Planning, Analysis, Design, Implementation
- Executed sequentially, incrementally, iteratively or in some other pattern.
SDLC: The Planning Phase 1. Project Initiation
- Develop/ receive a system request
- Conduct a feasibility analysis
2. Project Management
- Develop a work plan
- Staff the project
- Monitor & control the project
Deliverable: Project Plan
SDLC: The Analysis Phase 1. Develop an analysis strategy
- Model the current system
- Formulate the new system
2. Gather the requirements
- Develop a system concept
- Create a business model to represent business data and business processes
3. Develop a system proposal
Deliverable: System proposal
,SDLC: The Design Phase 1. Develop a design strategy
2. Design architecture and interfaces
3. Develop databases and file specifications
4. Develop the program design to specify:
- What programs to write
- What each program will do
Deliverable: System specification
SDLC: The Implementation Phase 1. Construct the system
- Build it (write the programming code)
- Test it
2. Install system
- Train the users
3. Support the system (maintenance)
Implementation: New system and maintenance plan
SD Methodology: Structured Development - Waterfall development
- Parallel Development
SD Methodology: Rapid Application Development - Phased
- Prototyping
SD Methodology: Agile Development - Extreme programming
- SCRUM
Object-Oriented Systems Analysis and Design (OOSAD) - Attempts to balance data and process
- Utilizes the Unified Modeling Language (UML) and the Unified Process
- Characteristics: Use-case driven, Architecture Centric, Iterative and Incremental
Classes & Objects - A characteristic of an object-oriented system
- Object (instance): instantiation of a class
- Attributes: information that describes the class
- State: describes its values and relationships at a point in time
, Methods & Messages - A characteristic of an object oriented system
- Methods: behavior of a class
- Messages: information sent to an object to trigger a method (procedure call)
Encapsulation & Information Hiding - A characteristic of an object oriented system
- Encapsulation: combination of process and data
- Information hiding: functionality is hidden
Inheritance - A characteristic of an object oriented system
- General classes are created (super classes)
- Subclasses can inherit data and methods from a superclass
Polymorphism & Dynamic Binding - A characteristic of an object oriented system
- Polymorphism: the same message can have different meanings
- Dynamic binding: type of object is not determined until run time
Contrast with static binding
Use-Case Driven Define the behavior of a system, each focuses on one business process
Architecture Centric - Functional (external) view: focuses on the user's perspective
- Static (structural) view: focuses on attributes, methods, classes, and relationships
- Dynamic (behavioral) view: focuses on messages between classes and resulting
behaviors
Iterative & Incremental Undergoes continuous testing and refinement, the analyst understands the system
better over time
Benefits of Object-Oriented Systems Analysis and Design - Break a complex system into smaller, more manageable modules
- Work on modules individually
