Podcast Beta
Questions and Answers
Which of the following is a characteristic of low-end project management tools?
What happens to assignments that are submitted more than three days late?
Which of the following tools is specifically mentioned as a midrange project management tool?
Which method is used for time management in project management?
Signup and view all the answers
What is the penalty for late submissions per day?
Signup and view all the answers
Which of the following is NOT considered a tool for managing project scope?
Signup and view all the answers
What encompasses the midrange tools of project management?
Signup and view all the answers
What is a defining feature of high-end project management tools?
Signup and view all the answers
What is the main purpose of architectural design in a system?
Signup and view all the answers
Which of the following is NOT a type of architectural diagram mentioned?
Signup and view all the answers
What does verification ensure in the context of system implementation?
Signup and view all the answers
Which type of testing does NOT require knowledge of the internal workings of the system?
Signup and view all the answers
What do validation activities primarily check in a system?
Signup and view all the answers
What is a common goal of using architectural diagrams?
Signup and view all the answers
In the context of verification, what does a report typically include?
Signup and view all the answers
Which of the following describes unit testing?
Signup and view all the answers
What does component/system testing typically use for evaluation?
Signup and view all the answers
Which of the following statements is true regarding supportability?
Signup and view all the answers
What is one of the primary purposes of a feasibility document for a project manager?
Signup and view all the answers
Which of the following is NOT considered an input for developing a project charter?
Signup and view all the answers
What formal document must key project stakeholders sign to indicate their agreement on a project's need and intent?
Signup and view all the answers
Which step follows the submission of the feasibility document for project authorization?
Signup and view all the answers
What does a feasibility document primarily help the client understand?
Signup and view all the answers
In the project approval process, who is responsible for preparing the feasibility study?
Signup and view all the answers
Which of the following is a value of the feasibility document for the performing organization?
Signup and view all the answers
What is a key output of project integration management?
Signup and view all the answers
What is the goal of Requirements Engineering?
Signup and view all the answers
Which of the following is a disadvantage of using text documents for requirements?
Signup and view all the answers
What is a major advantage of using Use Case Diagrams?
Signup and view all the answers
User Stories are particularly useful in which type of methodologies?
Signup and view all the answers
Which statement is true regarding Requirements Structuring?
Signup and view all the answers
What is one of the activities involved in Requirements Engineering?
Signup and view all the answers
What is a potential drawback of User Stories?
Signup and view all the answers
Which tool assists in understanding how users will interact with a software system?
Signup and view all the answers
What is the primary objective of User Experience Design?
Signup and view all the answers
Which advantage do Use Case Diagrams offer compared to text documents?
Signup and view all the answers
Which of the following is NOT a phase in software development?
Signup and view all the answers
What is an issue that arises with representing requirements in natural language?
Signup and view all the answers
What aspect of requirements management does change control focus on?
Signup and view all the answers
Which of the following best describes the 'FURPS' classification mentioned in requirements structuring?
Signup and view all the answers
What is one key purpose of a Work Breakdown Structure (WBS)?
Signup and view all the answers
Which rule ensures that elements in the WBS do not overlap in their definitions?
Signup and view all the answers
What format can a WBS be presented in?
Signup and view all the answers
What does the 100% rule in WBS imply?
Signup and view all the answers
What does a WBS NOT show?
Signup and view all the answers
Which of the following is a benefit of using a WBS?
Signup and view all the answers
What is the requirement for the quality of a WBS?
Signup and view all the answers
Which of the following statements about WBS is true?
Signup and view all the answers
Study Notes
Project Management Software
- Project Management software is available in 3 categories: Low-end tools, Midrange tools, and High-end tools
- Low-end tools are suitable for single/smaller projects and cost under $200 per user
- Midrange tools handle multiple projects and users, costing between 200−200-200−1,000 per user
- Microsoft Project is the most popular midrange tool
- High-end tools, also known as enterprise project management software, are often licensed on a per-user basis
- Several free or open-source tools are available including Jira, Clickup and Zoho
Project Management Tools and Techniques
- Project management tools and techniques assist project managers and their teams in various aspects of project management
- This includes scope, time and cost
- Scope includes tools such as: project charter, scope statement, and Work Breakdown Structure (WBS)
- Time management tools include: Gantt charts, network diagrams, critical path analysis, and critical chain scheduling
- Cost management tools include: cost estimates and earned value management
Marking Scheme
- The assessment will consist of an assignment-based project which is worth 30% of the final grade.
- It will also include a presentation which will be peer-evaluated
- Term tests are worth 60% of the final grade
- Quizzes and assignments will be worth 10% of the final grade
Phases of Software Development
- Software development is a progressive refinement which moves from concept to operations
- This involves several phases: Requirements & User Experience Design, Design, Implementation, Verification and Validation, Deployment, Operations and Maintenance
- The cost of change increases as we move along these phases
- Different processes place emphasis on each activity and define the order they are performed
Requirements Management
- The goal of requirements management is to form a shared view about the characteristics of the system to be built
- Outputs from requirement management are a list of requirements presented as: a text document, list of user stories, or a combination of diagrams and textual descriptions
- User stories follow the format: As a [user] I want to do [this] because [of that]
- User stories are a partial specification that require further detailing during implementation
- Use Case diagrams describe the interaction between users and the system
- Free or structured text detailing the functions and properties of a system is another output of requirement management
Requirements Engineering
- Requirements Engineering involves defining and maintaining requirements over time
- This involves: requirements elicitation, requirements structuring, user experience design, and requirements validation
Requirements Structuring
- The goal of requirements structuring is to improve the maintenance of requirements over time.
- This involves: isolating and identifying requirements for easy manipulation, organizing and classifying requirements, and annotating elements with information such as priority, importance, traceability
User Experience Design
- User Experience Design aims to provide a coherent and enjoyable experience for users when interacting with various aspects, including the system's: design, interface, interaction, and manuals.
- User centered analysis involves understanding user interactions with the system. This can involve: focus groups and experiments
- User centered design involves specifying how the user will interact with the system. This may use methods such as mock-ups.
Requirements Validation
- Requirements validation aims to identify and address inconsistencies in the requirements.
- This includes: scenario 1: R1 - Performance, Supportability
Architectural Design
- Architectural Design defines the system structure based on its components
- This structure is represented in diagrams: class diagrams, component diagrams, etc.
Implementation
- Implementation involves putting the requirements into practice based on the structure outlined in the architectural design.
- This is commonly achieved through writing code.
Verification and Validation
- Verification confirms whether the implementation works as expected
- Validation confirms whether the system fulfills the intended purpose outlined in the requirements
- Reports are generated for both verification and validation
- Different scope/representation types include: unit, component, or system.
- Different types of tests include: white-box testing (source code knowledge required) and black-box testing (no internal system knowledge required)
- Verification and validation use test types such as: Unit test, System test, and Integration test
Feasibility
- The feasibility document is valuable for the client, performing organization, and project manager.
- It helps with understanding the project direction, long and short-term perspectives, and the viability of the project moving forward
Project Approval Process
- The process for project approval varies, but typically involves these steps:
- Upon receiving a request, a preliminary project manager is identified
- The project manager prepares a feasibility study which is agreed with the customer and key stakeholders
- The project manager submits the document for authorization
- The document is analyzed, and a formal decision is made
- The project manager is officially appointed, and the project moves to the planning phase
Project Charter
- A project charter formally recognizes the existence of a project and provides direction on its objectives and management
- Key stakeholders should sign the project charter acknowledging agreement on the need and intent of the project.
- A signed charter acts as a key output of project integration management.
Inputs for Developing a Project Charter
- Several documents can be used as inputs for developing a project charter.
- These include: statements of work, business cases, agreements, enterprise environmental factors, and organizational process assets.
Work Breakdown Structure (WBS)
- A WBS is a visual representation of the project's deliverables
- It is a decomposition of the project scope into manageable tasks.
- It establishes the basis for defining the work, showing the relationships between activities, and identifying the organizational elements responsible for accomplishing the work.
- There are two formats for a WBS: graphical tree or textual outline
- It uses a decimal numbering system to identify elements
- It shows "is contained in" relationships, but not dependencies or durations.
WBS Rules of Thumb
- There should be no overlaps in the definition of the elements, and all work items should be included
- It doesn't need to be balanced with all paths reaching the same level
- The focus should be on the quality of the WBS
Studying That Suits You
Use AI to generate personalized quizzes and flashcards to suit your learning preferences.
Related Documents
Description
Explore the different categories of project management software, including low-end, midrange, and high-end tools. Learn about the key features, costs, and popular examples such as Microsoft Project and free alternatives like Jira and Clickup. This quiz will also cover essential tools and techniques for effective project management.
