System – an array of components designed to accomplish a particular objective  Concept

according to plan.  Development

System Thinking – way of understanding an entity in terms of its purpose.  Implementation
System Integration – is a combination of inter-related elements to achieve a  Support
common objective. System Development Life Cycle (SDLC) - is a framework for describing the
System Architecture – high level structure, exposing its gross organization as a phases involved in developing and maintaining information systems
collection of interacting components.  Systems development projects can follow
• Elements needed to model a software architecture include:  Predictive models: The scope of the project can be clearly
1. Components 3. Systems articulated and the schedule and cost can be predicted.
2. Connectors 4. Properties & Styles  Adaptive models: Projects are mission driven and component
Project - is a temporary endeavor undertaken to accomplish a unique product or based, using time-based cycles to meet target dates.
service.
Problems - are undesirable situations that prevent the business from fully 5 Predictive Life Cycle Models
achieving its purpose, goals, and objectives  waterfall model has well-defined, linear stages of systems development
Opportunity – is a chance to improve the business even in the absence of specific and support.
problems.  spiral model shows that software is developed using an iterative or spiral
Directive – is a new requirement that is imposed by management, government, approach rather than a linear approach.
or some external influences i.e., are mandates that come from either an internal  incremental release model provides for progressive development of
or external source of the business. operational software.
4 Frames  prototyping model is used for developing prototypes to clarify user
Structural Frame - Focuses on roles and responsibilities, coordination and control. requirements.
Organizational charts help define this frame.  RAD model is used to produce systems quickly without sacrificing quality.
Political Frame - Assumes organizations are coalitions composed of varied Adaptive Life cycle Models
individuals and interest groups. Conflict and power are key issues.  Extreme Programming (XP): Developers program in pairs and must
Human resources frame - Focuses on providing harmony between needs of the write the tests for their own code. XP teams include developers,
organization and needs of people. managers, and users.
Symbolic Frame - Focuses on symbols and meanings related to events. Culture is  Scrum: Repetitions of iterative development are referred to as sprints,
important. which normally last thirty days. Teams often meet every day for a short
meeting, called a scrum, to decide what to accomplish that day. Works
Basic organizational structures best for object-oriented technology projects and requires strong
Functional Structure - People who do similar tasks, have similar skills and/or jobs leadership to coordinate the work
in an organization.
Divisional Structure - coordinate inter-group relationships to create a work team
that can readily meet the needs of a certain customer or group of customers.
Matrix structures - are more complex in that they group people
Project Organization Structure - teams are put together based on the number of
members needed to produce the product or complete the project.
Project Life Cycle – is a collection of project phases.
 constraints. These can be categorised into 2; functional requirements and
non-functional requirements
 Functional requirements
 Describe what the system should do
 Non-functional requirements
 Consists of Constraints that must be adhered to during
development (design and implementation)
 Remember ‘Constraints.’
Examples of Non- Functional Requirements
 Interface requirements
 Performance
 Security
 Operating Requirements
 Lifecycle Requirements
 Limits om Development
Requirements - are statements that identify the essential needs of a system in  Economic Requirements
order for it to have value and utility. Requirements Documentation
Requirements Life Cycle two types of documents realized from the requirements elicitation phase
1. Elicitation Phase - involves a number of people to ensure • User Requirements Specification Document - The URS document
consideration of a broad scope of potential ideas and candidate problems outlines precisely what the User (or customer) is expecting from
2. Organization Phase - is no transformation of the requirements, but this system. User Requirement Specification may incorporate the
simple classification and categorization. functional requirements of the system or may be in a separate
3. Analysis Phase - This represents a transformation. document labelled the Functional Requirements Specification -
4. Prototype Phase - poorly understood requirements may be tested and the FRS.The URD has the following information:
perhaps strengthened, corrected, or refined. - Functional Requirements
5. Requirement’s documentation and specification - Non-Functional Requirements
System Requirements • System requirements specification Document - A detailed
• Characteristics or features that must be included to satisfy business description of the system services.
requirements TOOLS THAT AID IN DEVELOPING & UNDERSTANDING SYSTEM
• Outputs REQ’TS
• Inputs • Affinity diagrams
• Processes • Force-field analysis
• Timing • Ishikawa fishbone (cause-and-effect) diagrams
• Controls • Pareto diagrams
• Volumes. sizes, and frequencies • Pugh charts
Types of Requirements • Quality function deployment (QFD)
 User Requirements: these are statements in Natural language plus
diagrams of services the system provides, together with its operational