Untitled document.docx

Module 1: Software and Software Engineering ------------------------------------------- ### **Software** - #### **Types of Software** - - - - - - #### **Software Characteristics** - #### **Software Application Domains** - #### **Legacy of Software** - ##...

Module 1: Software and Software Engineering ------------------------------------------- ### **Software** - #### **Types of Software** - - - - - - #### **Software Characteristics** - #### **Software Application Domains** - #### **Legacy of Software** - #### **Overview of Software Engineering** - - - - ### The Software Process - - - - - - ### Software Engineering Practices and Principles #### **Software Engineering Practices** - - ### General Principles - #### **First Principle: The Reason It All Exists** - #### **Second Principle: KISS (Keep It Simple, Stupid!)** - #### **Third Principle: Maintain the Vision** - #### **Fourth Principle: What You Produce, Others Will Consume** - #### **Fifth Principle: Be Open to the Future** - #### **Sixth Principle: Plan Ahead for Reuse** - #### **Seventh Principle: Think!** - ### Software Myths - #### **Management Myths** - #### **Customer Myths** - #### **Practitioner Myths** - Module 2: Understanding Requirements, Project Management Concepts, Product, Process, and Project Metrics -------------------------------------------------------------------------------------------------------- ### Lesson 1: Key Concepts #### **Requirements Engineering** - ### Establishing Ground Work - #### **Identifying Stakeholders** - #### **Recognizing Multiple Viewpoints** - #### **Workflow Toward Collaboration** - #### **Asking the First Questions** - #### **Nonfunctional Requirements** - #### **Traceability** - ### Eliciting Requirements - #### **Collaborative Requirements Gathering** - - - #### **Elicitation Work Products** - - #### **Agile Requirements Elicitation** - ### Negotiating Requirements - #### **Requirements Monitoring** Requirements Monitoring is useful when incremental development is used. It encompasses [five tasks]: - ### Key Concepts **What is it?** - **Why is it important?** - **What are the steps?** - - **What is the work product?** - ### The People #### **The Stakeholders** - - #### **Team Leaders** - - - - #### **Software Team** - - ### The Product #### **Software Scope** - - #### **Problem Decomposition** - - ### The Project - - - - ### Metrics in the Process and Project Domains - - #### **Classification of Software Metrics** - - - - #### **Types of Metrics** - **Module 3:The Process Models, Agile Development, and Modeling Principles that guide Practices** ------------------------------------------------------------------------------------------------ ### Prescriptive Process Models - #### **Waterfall Model** - #### **Incremental Process Models** - #### **Evolutionary Process Models** - #### **Prototyping** - #### **Spiral Model** - #### **Concurrent Models** - ### Specialized Models - #### **Component-Based Development** - #### **Formal Methods Model** - #### **Aspect-Oriented Software Development** - ### The Unified Process #### **The Unified Process** - #### **Phases of the Unified Process** - - - ### Personal and Team Process Models #### **Personalized Software Process** - - #### **Team Software Process** - #### **Process Technology** - #### **Agile** - #### **Agility Principles** - - #### **Extreme Programming** - - #### **Industrial XP** - - - - - - - - - - - - - #### **Other Agile Process Model** - - - #### **Toolset for the Agile Process** - - -