The document provides an overview of software engineering methodologies and the management aspects of software projects, including planning, organizing, staffing, and monitoring. It discusses the importance of project management, risk management, quality management, and configuration management in software development. Additionally, it outlines key considerations for managing software projects, such as resource allocation, budgeting, and controlling project dimensions like time, information, organization, quality, and cost.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
4 views
Topic 2 SE & Management
The document provides an overview of software engineering methodologies and the management aspects of software projects, including planning, organizing, staffing, and monitoring. It discusses the importance of project management, risk management, quality management, and configuration management in software development. Additionally, it outlines key considerations for managing software projects, such as resource allocation, budgeting, and controlling project dimensions like time, information, organization, quality, and cost.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12
Topic 2
Software Engineering and
Management : An Overview Software Engineering Methodologies • Discussion on Software Engineering Methodologies – All the relevant models in software engineering : an overview – To compare various models of software engineering and development. Software Management In general management aspect of a software project management involves:- • Planning – deciding what is to be done • Organising – making arrangement • Staffing – selecting the right people for the job • Directing – giving instructions • Monitoring – checking on progress • Controlling – taking action to remedy hold-ops • Innovating – coming up with new solutions • Representing – liaising with clients, users, developer, suppliers and other stakeholders. Software Management Extended from software engineering is the management aspect of the software:
• Software Project Management
– Along with project planning, risk management, people management, and team working • Project planning and estimation – Fundamental planning tools, plan driven development, agile method, software cost estimation • Quality Management – Process and techniques – Standards in quality management Software Management • Configuration Management – Important for large systems – Configuration planning – Version management – System building – Change management • Software Process Improvement – SEI capability-based approach – Capability maturity models Software Management • Is essential part of software engineering • is a broad term that can also apply to financial management, network management, customer relationship management, asset management or inventory management. Managing Software Projects • Questions:- – How must people, process and problem be managed during a software project? – How can software metrics be used to managed a software project and the software process? – How does a software team generate reliable estimates of effort, cost, and project duration? – What techniques can be used to assess the risks that can have an impact on project success? – How does a software project manager select a set of software engineering work tasks? – How is a project schedule created? – Why are maintenance and reengineering so important for both software engineering managers and practitioners? Managing Software Projects • Software development projects involve several people, for prolonged period of time. • Large projects may range over several years and involve hundreds of people. • Such projects must be carefully planned and control. Managing Software Projects - Planning • Introduction – introduce to the project plan, the background and history of the project, the aims, the project deliverable, the names of person responsible and summary. • Process model – which activities are to be undertaken, milestones and which critical paths. • Organisation of the project – the relationship of the project to other entities, and within the project team. • Standards, guidelines, procedures – must be stated and implemented with support tools. • Management activities – are guided by goals and priorities set for the project. Managing Software Projects - Planning • Risk – Potential risks have to be identified. Example, hardware may not be delivered on time, qualified personnel may not be available, etc. • Staffing – different points in time requires different amount of personnel with different skills. • Method and Techniques- during requirements engineering, design, implementation and testing. • Quality Assurance – Quality assurance to be used throughout the development • Work packages – broken down into activities, manageable pieces to be identified. Managing Software Projects - Planning • Resources – The hardware, CPU, tools. Also indicate the personnel needed for the various process phases. • Budget and Schedule – The total budget for the project has to be allocated, and indicated to the work breakdown structure. • Changes – Changes need to be managed, reviewed, documented. Handle by configuration control plan. • Delivery – The procedure to be followed in handing over the system to the customers. Controlling Software Project • Five dimensions:- – Time : How do we assess progress towards the project’s goals? – Information : How do we handle the documents that are produced? – Organisation: How do we organise the project team and coordination – Quality: How do we define and assess quality requirements – Money: How do we estimate the cost of a project?