tailieunhanh - Applied Software Project Management - LESSON 2: SOFTWARE PROJECT PLANNING

Most software is built in organizations for people with specific needs. A stakeholder is a anyone who has an interest (or stake) in the software being completed A user is someone who will need to use the software to perform tasks. Sometimes stakeholders will be users; but often the stakeholder will not use the software. For example, a senior manager (like a CEO - chief executive officer or CTO - Chief technology officer in a company) will usually have a stake in the software that is built (since it affects the bottom line), even if she won’t ever use it | LESSON 2: SOFTWARE PROJECT PLANNING Applied Software Project Management 5/13/2020 10:42:33 PM 5/13/2020 10:42:33 PM WHO NEEDS SOFTWARE? Most software is built in organizations for people with specific needs. A stakeholder is a anyone who has an interest (or stake) in the software being completed A user is someone who will need to use the software to perform tasks. Sometimes stakeholders will be users; but often the stakeholder will not use the software. For example, a senior manager (like a CEO - chief executive officer or CTO - Chief technology officer in a company) will usually have a stake in the software that is built (since it affects the bottom line), even if she won’t ever use it. STAKEHOLDER: - SPONSOR - CUSTOMER - FUNCTIONAL/MANAGERS - PROJECT MANAGER - PROJECT TEAM MEMBER 5/13/2020 10:42:33 PM CLASSIFYING STAKEHOLDERS 5/13/2020 10:42:33 PM Example: Classifying stakeholders – an airline booking system An international airline is considering introducing a new booking system for use by associated travel agents to sell flights directly to the public. Primary stakeholders: travel agency staff, airline booking staff Secondary stakeholders: customers, airline management Tertiary stakeholders: competitors, civil aviation authorities, customers’ travelling companions, airline shareholders Facilitating stakeholders: design team, IT department staff WHO BUILDS SOFTWARE? Software is typically built by a team of software engineers, which includes: Business analysts or requirements analysts who talk to users and stakeholders, plan the behavior of software and write software requirements Designers and architects who plan the technical solution Programmers who write the code Testers who verify that the software meets its requirements and behaves as expected 5/13/2020 10:42:33 PM PROJECT MANAGEMENT The project manager plans and guides the software project The project manager is responsible for identifying the users and stakeholders and . | LESSON 2: SOFTWARE PROJECT PLANNING Applied Software Project Management 5/13/2020 11:56:42 PM 5/13/2020 11:56:42 PM WHO NEEDS SOFTWARE? Most software is built in organizations for people with specific needs. A stakeholder is a anyone who has an interest (or stake) in the software being completed A user is someone who will need to use the software to perform tasks. Sometimes stakeholders will be users; but often the stakeholder will not use the software. For example, a senior manager (like a CEO - chief executive officer or CTO - Chief technology officer in a company) will usually have a stake in the software that is built (since it affects the bottom line), even if she won’t ever use it. STAKEHOLDER: - SPONSOR - CUSTOMER - FUNCTIONAL/MANAGERS - PROJECT MANAGER - PROJECT TEAM MEMBER 5/13/2020 11:56:42 PM CLASSIFYING STAKEHOLDERS 5/13/2020 11:56:42 PM Example: Classifying stakeholders – an airline booking system An international airline is considering .

• Kỹ thuật lập trình
• Software Problem
• Software Processes
• microsoft Project Management
• Specification
• Functional Specification
• Use Cases
• software engineering
• Lecture Software engineering
• Software development methods
• Problem frames
• Problem domain modeling
• Recombining problem frames
• Software architecture
• Problem structure
• Architectural decisions
• Dynamic capacitated maximal covering location problem
• Considering dynamic capacity
• Commercial software packages
• Multi period MCLP
• NP hard and commercial software packages
• Requirements Analysis
• Simple workpieces
• Required behavior
• Software Process Models
• Dependent on software
• Problem statement
• Basic requirements
• Capacitated transportation problem
• Enhanced flow
• Quadratic transportation problem
• Software GAMS
• Feasible solution
• Assignment problem
• Network simplex algorithm
• Computer algorithms
• Transportation problem
• Educational methods
• Programming and problem solving with C++
• Comprehensive edition
• Problem Solving techniques
• C++ program structure
• Value Returning functions
• Software design methodologies
• Mathematical programming
• Combinatorial optimization
• Optimization software
• Minimum cost network flow problem
• Optimization software packages
• Lecture Software design
• Software design
• Bài giảng Thiết kế phần mềm
• Possible solution
• UML class diagram