System Life Cycle in Project Management

System Life Cycle

• A conceptual model used in project management (PM) that describes the stages in an information system (IS) development project, from initial feasibility study to maintenance.

Planning/Initiation

• Foundation of the entire System Development Life Cycle (SDLC).
• Clearly defines the project's target and assesses solving specific problems via software solutions.
• Key Objectives: Problem identification, resource and cost estimations, requirement gathering, and setting expectations/goals.
• Includes pre-analysis utilizing simulation tools, resource estimation, allocation, and deadline setting.

Analysis/Feasibility

• Determines the project's technical, operational, and economic feasibility.
• Aims to translate high-level plans into actionable development ideas.
• Bridges the gap between project conception and actual development.
• Key Objectives: System requirement analysis, project feasibility assessment, and gathering information about system and client requirements, market research etc.

Design

• Visualization-focused phase.
• The systems architect designs the system and creates the first software prototype, showing its function.
• A key milestone in software development, shifting from concepts to outputs.
• Aspects of design include: system interface, user interface, security, and database.

Development

• The coding phase, where actual code is written.
• Aims to develop functional, efficient, and user-friendly software.
• Adheres to Software Design Documents (SDD) and coding guidelines.
• Involves coding, debugging (identifying and fixing errors), and using appropriate programming languages.

Testing

• Critical phase to ensure the software application meets required specifications.
• Employs processes like bug detection, vulnerability testing, defect identification, and verification/validation.
• Ensures the application functions correctly.

Implementation

• The designed system is brought to life and implemented.
• Supports planned business operations by successfully deploying the new system.
• Key objectives include system deployment, user onboarding, and performance evaluation; the successful rollout and usability of the newly developed system.

Maintenance

• Handling issues reported by end-users, maintaining and improving system performance.
• Addressing issues, improving performance, and adapting the system to evolving requirements.
• Includes continuous monitoring, maintenance activities (corrective, adaptive, perfective), and ongoing support.

SDLC Models

• Waterfall: Linear, sequential approach, each stage is a separate plan. No feedback loop.
• Iterative: Combines sequential steps with iterative design for improvements and changes. Early feedback is valuable.
• Spiral: Combines Waterfall and Iterative models, using loops to refine complex projects with fluctuating requirements. High uncertainty is accommodated.
• V-Model: A variation of the Waterfall model with a corresponding testing phase for each stage. Early error detection is key to cost effective development.
• Agile: Focuses on collaboration between teams and implementing client feedback early and often, for adaptable and well-received software. Quick iterations, high stakeholder feedback loops.
• Big Bang: Simplifies model by combining efforts, time, and resources, sometimes compromising completeness.

System Analysis & Design

• Structured approach to developing, maintaining and improving information systems within an organization.
• Analysts plan, develop and maintain information systems, managing IT projects and/or reporting to other departments.
• Benefits from systems analysis and design include: Better decision-making, increased efficiency, cost savings, and aligning with business goals.
• Requirements Gathering Techniques:
  • Interviews: Direct discussions with stakeholders.
  • Surveys: Gathering data from multiple sources.
  • Observation: Watching user interactions in the system.
  • Document analysis: Evaluating existing documentation relating to user needs.
  • Joint Application Development (JAD): Group discussions for user input.

Data Flow Diagrams (DFD)

• Graphical representation of data movement within a system.
• A visual technique created by Larry Constantine for illustrating systems requirements.
• Various levels (e.g. 0, 1, 2, 3) provide different levels of detail.

Data Dictionary

• A structured repository of data elements in a system.
• Plays a crucial role in database design, providing details on data types, constraints and descriptions for each data element.
• Categorized (e.g. Data elements, data flows, and data stores) and can be active or passive.

Data Modeling

• Creating a visual representation of system data.
  • Includes its relationships, use and storage.
• Used for efficient development and design in software development.
• Types: Physical, Logical, Conceptual data modeling.

System Design

• Defines the architecture and detailed specifications of the overall system, ensuring it addresses user requirements, meeting specified standards.
• Includes Logical (user-focused) and Physical (technical) design considerations, including architectural decisions, making sure the design meets project standards.

User Interface (UI) Design

• The design of user interact elements. Key principles such as consistency, accessibility, simplicity, and feedback should be adhered to to build a useful and user friendly system.