TECHNICAL AREAS (5 KAs) OF SOFTWARE ENGINEERING
Also called the Software Development Life Cycle (SDLC) processes
REFER TO DIAGRAM at http://en.wikipedia.org/wiki/Waterfall_model <== Must go here.
(1) Software requirements
(2) Software design
(3) Software construction
(4) Software testing
(5) Software maintenance
MANAGEMENT AREAS (5 KAs) OF SOFTWARE ENGINEERING
(6) Software configuration management
(7) Software engineering project management
(8) Software engineering process management
(9) Software engineering tools and methods
(10) Software quality (product quality versus process quality)
SE is about developing, operating and maintaining SOFTWARE in a manner that is systematic, disciplined and quantifiable, right?
===========================================================
TODAY IS FOR PROJECT MANAGEMENT Item (7) above. We will use a CASE tool (openproj)
CASE = Computer Aided Software Engineering.
Every and all of the above 10 topics ==> are related. Why?
What is a project?
How can you execute a project if you do not know the requirements?
What is your particular project about?
GATHERING INFORMATION (W5H2 PRINCIPLE)
===========================================================
What
Why
Who
When
Where
How
How much/many
MANAGEMENT (PRMCC)
===========================================================
P ==> Planning
R ==> Review and Update of plans
M ==> Measure and Monitor progress of plans.
C ==> Control. Make the right decisions at right times when required.
C ==> Coordinate. (with other people or team members).
===========================================================
PROJECT MANAGEMENT TERMS.
Project
Task
Duration
Work Breakdown Structure WBS
Timeline
Resources
Estimated Costs
Slack
Critical Path
Predecessor task
Successor task
Milestone
Gantt Chart
===========================================================
Risk Management
Contingency Plan / Backup Plan
Primavera software
SVN software (Version Control)
Git software
Plan versus Strategy
MANAGING RISKS
(1) Probability of risky event happening (unlikely to happen, medium chance, very likely to happen).
(2) Impacts of risky event when it happens. (small, medium, serious and catastrophic impacts)
IDENTIFY RISKS
ASSESS RISKS
MITIGATE RISKS
===========================================================
--
WASSALAM
wruslan.hahaha
Summary of Software engineering project management
===========================================================
- Software Project Planning & Control. CASE Tools (OpenProj)
- Considerations in Project Management (4 Ps), Product, People, Process and Project.
- The Project Manager like a "Movie Director". Visioning everything before starting the project.
- The five(5) steps in project scheduling and their outputs.
- Plan the tasks to be executed in the project. This requires EXPERIENCE and DOMAIN KNOWLEDGE.
- Estimate the resources and time durations required for the tasks.
- Analyse the plan for managing its implementation.
- Identify the deliverables at the milestones
- Perform project risk management
- Software Engineering Metrics. Estimation Model. Lines of code (LOC), Source S(LOC), Function Points (FP).
- Decomposition Techniques and Planning tools. (OpenProj)
- Gantt Chart, tasks, milestones, critical path, slacks, Resource Usage Table, Work Breakdown Structure (WBS), predecessors, etc.
- Types of project managements decisions and their impacts, etc.
- PRMCC in Management - Planning, Reviewing, Measuring and Monitoring, Controlling, and Coordinating.
- SMART task characteristics - specific, measurable, achievable, realistic and time-bound.
Microsoft Word Version
Return to Software Engineering Fundamentals (SEF9MMUWRY)
Previous Topic: 15 If you have problems with Java for openproj-1.4-2 installation
Next Topic: 17 Resources for Tutorial 3 (Software Design)
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment