ch 2 pm

 Here's a breakdown of the Software Engineering Institute's (SEI) Capability Maturity Model Integration (CMMI) framework elements, particularly relevant to the Unified Process (UP) and other structured methodologies:

Framework Elements:

Life Cycle Phases:

  • Inception: Focuses on establishing the project's vision, scope, business case, and feasibility.
  • Elaboration: Defines the architecture, refines requirements, and plans the remaining project. Mitigates high-risk elements.
  • Construction: Iteratively develops and integrates the bulk of the software, building working versions.
  • Transition: Deploys the software to the user community and ensures operational readiness. (Note: Your request mentioned "training phase" which often aligns with Transition activities.)

Artifacts of the Process:

  • The Artifact Sets (Categories):
    • Management Artifacts: Pertain to project planning, tracking, and control (e.g., business case, project plan, risk list).
    • Engineering Artifacts: Core technical deliverables (e.g., requirements, design models, source code, test cases).
    • Pragmatics Artifacts: Support the practical execution and environment (e.g., development environment configuration, process definitions, standards).

Model-Based Software Architectures:

  • Emphasizes using models (UML diagrams, architectural patterns) as primary artifacts to define, understand, and communicate the system's structure and behavior before and during coding. This promotes clarity, reusability, and maintainability.

Workflows of the Process:

  • Represent the sequence of activities performed by different roles to produce artifacts. Common workflows include:
    • Requirements: Eliciting, analyzing, documenting, and validating needs.
    • Analysis & Design: Transforming requirements into an architectural and design model.
    • Implementation: Coding and unit testing components.
    • Test: Verifying and validating the integrated system.
    • Deployment: Delivering the system to the users.
    • Configuration & Change Management: Managing evolving artifacts.
    • Environment: Setting up and maintaining the development infrastructure.
    • Management: Planning, organizing, and controlling the project.

Checkpoints of the Process:

  • Formal review points where key stakeholders assess project status, risks, and readiness to proceed to the next phase. They ensure alignment with objectives and provide opportunities for course correction. Examples often tied to phase completion:
    • Lifecycle Objective (LCO): End of Inception. Confirms project vision and feasibility.
    • Lifecycle Architecture (LCA): End of Elaboration. Validates architecture and project plan.
    • Initial Operational Capability (IOC): End of Construction. Demonstrates a usable product.
    • Product Release (PR): End of Transition. Final product delivery.

Comments

Post a Comment

Popular posts from this blog

pm unit :1

Evolution of software economics. short and efficient: The evolution of software economics reflects a shift from a "craft" to a more industrialized, predictable process. Early Days (1960s-1970s - Conventional/Craftsmanship): Characteristics: Custom tools, custom processes, primarily custom components built in primitive languages. Economics: Highly unpredictable; cost, schedule, and quality objectives were frequently underachieved. Focus was on basic analysis and coding. Transition (1980s-1990s - Software Engineering): Characteristics: Emergence of repeatable processes and off-the-shelf tools. Higher-level languages became prevalent. Some commercial components (OS, databases, networking) were adopted. Economics: Still somewhat unpredictable, but improvements in process and tooling started to offer better control. Software cost models like COCOMO emerged to estimate effort based on factors like size, process, personnel, environment, and quality. Modern Practices (2000...
Read more

ch 3 pm

  Iterative Process Planning: Instead of a single, rigid plan, this involves continuous refinement of project plans in small cycles (iterations). Each iteration builds on the last, allowing for flexibility, early feedback, and adaptation to changing requirements and risks. This is a hallmark of Agile methodologies. Project Organizations and Responsibilities: Defines the roles, responsibilities, and reporting structures within a software development team (e.g., project manager, architects, developers, testers). It also addresses how teams are structured (e.g., functional, matrix, cross-functional) to maximize efficiency and communication. Process Automation: Leveraging tools and scripts to automate repetitive and error-prone tasks across the software development lifecycle. This includes automated builds, testing (Continuous Integration/Delivery - CI/CD), deployment, environment provisioning (Infrastructure as Code), and reporting, significantly boosting efficiency and quali...
Read more