Software Engineering CP317 Project Management
16 Questions
0 Views

Choose a study mode

Play Quiz
Study Flashcards
Spaced Repetition
Chat to Lesson

Podcast

Play an AI-generated podcast conversation about this lesson

Questions and Answers

Which of the following is NOT a key benefit of using document management systems in software engineering?

  • Ensuring consistent data flow across teams
  • Providing clear direction for work
  • Preventing conflicts and miscommunications
  • Eliminating the need for team meetings (correct)

    • What is the primary purpose of a Requirements Document in software engineering?

  • To specify the desired features, functionalities, and constraints of the software (correct)
  • To define the detailed design of individual software modules
  • To outline the technical architecture of the software system
  • To record the testing procedures and results of the software

    • What is the main difference between a System Design Document and a Software Specification Document?

  • The System Design Document is more detailed than the Software Specification Document
  • The System Design Document covers the overall system architecture, while the Software Specification Document details individual components (correct)
  • The System Design Document is written before the Software Specification Document
  • The System Design Document is primarily for internal use, while the Software Specification Document is for external stakeholders

    • Which of the following is NOT a typical feature of a robust document management system?

    <p>Automatic code generation from design documents (B)</p> Signup and view all the answers

    During which phases of the software development life cycle are documentations crucial?

    <p>Throughout the entire software development process (C)</p> Signup and view all the answers

    Why is it important to set up a document tracking system at the beginning of a software project?

    <p>To ensure that all team members have access to the latest version of the documents (C)</p> Signup and view all the answers

    What does the term "Design" encompass within the context of a Software Specification Document?

    <p>The implementation of specific algorithms and data structures (A)</p> Signup and view all the answers

    Which of the following is NOT considered a core software engineering task?

    <p>Market research and analysis (D)</p> Signup and view all the answers

    What is the purpose of Software Testing Procedures?

    <p>All of the above. (D)</p> Signup and view all the answers

    What is the critical path in a project?

    <p>The longest duration path through the project network activities. (A)</p> Signup and view all the answers

    What is the single variable in the Static Single Variable Model for software cost estimation?

    <p>The size of the software project. (A)</p> Signup and view all the answers

    What is the purpose of using Pert Charts in project management??

    <p>All of the above. (D)</p> Signup and view all the answers

    What is the main benefit of using Gantt charts in project management?

    <p>To visualize the project schedule. (B)</p> Signup and view all the answers

    What are the four Ps of software project management?

    <p>People, Project, Process, Product (C)</p> Signup and view all the answers

    What is the main purpose of document revision history?

    <p>All of the above. (D)</p> Signup and view all the answers

    What is the COCOMO model used for?

    <p>All of the above. (D)</p> Signup and view all the answers

    Flashcards

    Software Engineering

    A field focused on the systematic design, development, and maintenance of software.

    Project Management

    The discipline of planning, executing, and closing projects to achieve specific goals.

    Document Change Control

    A systematic approach to managing changes made to documents during a project.

    Types of Documentations

    Includes requirements, design specifications, and user manuals used throughout software development.

    Signup and view all the flashcards

    Gantt Charts

    Visual tools that represent project schedules showing tasks over time.

    Signup and view all the flashcards

    COCOMO Model

    A software cost estimation model based on project size and complexity.

    Signup and view all the flashcards

    Risk Management in Projects

    The process of identifying, assessing, and mitigating risks that could impact project success.

    Signup and view all the flashcards

    Document Management Features

    Key features include document sharing, version control, and change tracking for effective management.

    Signup and view all the flashcards

    Software Coding Standard

    A set of guidelines for programming practices.

    Signup and view all the flashcards

    4 P’s of Software Project Management

    Focus areas: People, Product, Process, Project.

    Signup and view all the flashcards

    PERT Chart

    A graph showing task precedence in a project using nodes and links.

    Signup and view all the flashcards

    Critical Path Method

    A planning technique determining the longest duration path in project tasks.

    Signup and view all the flashcards

    Software Cost Estimation Models

    Frameworks for estimating the cost and effort of software projects.

    Signup and view all the flashcards

    Study Notes

    Software Engineering - CP317 Project Management

    • The course CP317 Software Engineering covers project management for weeks 1-2.
    • The instructor is Shaun Gao, Ph.D., P.Eng.
    • Review of week 1-1 is included in the course.
    • Topics for week 1-2 include documentation (document change control, types of documentation), project management (concept, PERT charts, critical path methods, Gantt charts), project management tools (software cost estimation models, COCOMO, Static Single Variable Model, Static Multi-Variable Model), and risk management.

    Documentation

    • Documentation is critical throughout the software engineering lifecycle.
    • A document tracking system should be established at the start of the project.
    • Benefits of using documents include keeping the team on track, providing clear direction, preventing conflicts, and producing high-quality products.
    • Good document management systems support document sharing, version control (preventing simultaneous changes), and searching (by keywords).
    • Examples of such systems include Rational ClearCase and database systems.
    • Different documentation types include Requirements, System Design, Software Specification, Design (data types, structures, object-oriented design), Software coding standard (guidelines for programming, unit testing and integration procedures), Meeting notes, and Release notes.
    • Document revision history should include Revision, Author, Date, Status and Description.

    Project Management

    • Project management is the application of processes, methods, skills, and knowledge to achieve project objectives.
    • Project acceptance criteria and agreed parameters are necessary for project management.
    • Project successes depend on managing goals (setting, tracking, and meeting them) and keeping the team focused on issues at hand.
    • Successful software project management requires focusing on People, Product, Process, and Project (4 P's).

    Project Management Tools

    • PERT Charts:

      • PERT (Program Evaluation and Review Technique) charts are graphical representations of project tasks, showing precedence relationships.
      • The formats can vary.
      • An example includes nodes, representing tasks, and links representing dependencies.
      • Charts will show activity duration dependency.

    • PERT Charts Examples:

      • Includes assignments and planning.
      • Examples contain task start, activity duration, and project milestones.
      • Example also shows multi-path charts, and analysis time estimations on charts.

    • Critical Path Methods:

      • The critical path method identifies the longest duration path through the project's network activities.
      • If any task on the critical path is delayed, the entire project completion is delayed.
      • Benefits of using Critical Path methods include clarity in identifying important tasks and visualizing project progress.
      • Benefits also include helping manage deadlines, comparing planned vs. actual status, identifying critical activities needing attention, as well as making dependencies in the project clear and transparent.

    • Gantt Charts:

      • Gantt charts are bar graphs that show project schedules over time.
      • Invented by Henry Gantt in the 1910s.

    • Gantt Chart Advantages:

      • Simple and clear presentation of task durations and schedules.
      • Help to schedule and visualize overall resource usage.

    • Gantt Chart Disadvantages:

      • Difficulty in visualizing dependencies between tasks.
      • Changes in data can drastically affect the visualizations.

    • Software Cost Estimation Models:

      • Software cost estimation model concepts including COCOMO, Static Single-Variable, and Static Multi-Variable Models.

    • COCOMO Model:

      • The Constructive Cost Model (COCOMO) is a software cost estimation model developed by Barry Boehm.
      • The basic COCOMO equations are used to calculate effort, deployment time, staff size, and productivity based on lines of code (KLOC).

    • Static Single Variable Model:

      • This model estimates effort, costs, and development time based on a single variable (Lines of Code -LOC).
      • Uses equations based on LOC to predict Effort (man-months), and Development Time (months).

    • Static Multi-Variable Model:

      • This model estimates effort, costs, and development time using multiple variables (internal and external) affecting the project.
      • Uses equations with multiple variables to estimate effort (man-months), and development time (months).

    Risk Management

    • Risk management is a process that allows understanding and managing risks proactively.
    • It reduces potential threats and maximizes opportunities to facilitate project success.
    • The key is focusing on resources (People, Product, Process, Project - 4Ps).

    Additional Information

    • Find group members by January 2025
    • Send email including group members' names and student IDs.
    • Assist with group formation if needed.

    Studying That Suits You

    Use AI to generate personalized quizzes and flashcards to suit your learning preferences.

    Quiz Team

    Related Documents

    Software Engineering Project Management Week 1-2 PDF

    Description

    This quiz covers project management topics from the Software Engineering course CP317, focusing on weeks 1-2. Learn about documentation types, project management concepts, PERT charts, Gantt charts, and risk management strategies. Prepare to enhance your understanding of project management tools and best practices in software engineering.

    More Like This

    Use Quizgecko on...
    Browser
    Open
    Browser
    Browser