Ingeniería de Software: 1st Review

Ingeniería de Software: 1st Review

5 phases of Software Engineering

1. Introduction
2. Project Management
3. Requirement Gathering
4. Development and Testing
5. Implementation. Metrics and Maintenance.

What is Software Engineering?

• "An organized, analytical approach to the design, development, use, and maintenance of software."
• More intuitively, software engineering is everything you need to do to produce successful software
• It includes the steps that take a raw, possibly nebulous idea and turn it into a powerful and intuitive application
• Software isn't physical. It exists only in the virtual world of the computer. Easy to make any changes
• The flexibility granted to software by its virtual nature is both a blessing and a curse

FACT: Unfortunately, the flexibility that allows you to make changes throughout a software project's life cycle also lets you mess things up at any point.

Why is Software Engineering important?

• There are countless ways that a simple concept can go wrong
• Programmers may not understand what users want or need
• The program might be so full of bugs that it's frustrating to use

What you will learn in Project Management?

1. What project management is and why you should care
2. How to use PERT charts, critical path methods, and Gantt charts to create project schedules and estimate project duration
3. How you can improve time estimates. Planning Poker
4. How risk management lets you respond quickly and effectively to problems
5. Keep track of what's going on in real time
   

Top Challenges with Planning & Estimation

• Ambiguous/changing requirements
• Difficult to predict exactly
• Takes too long
• Provided by wrong people
• Sofwatre Projects unique and ambiguous
• Promise unrealistic deadlines
• High level estimates
• Fixed Scope, time budget.

Software Project Manager

• Undertakes the responsibility of executing the software project and is thoroughly aware of all the phases that the software would go through.
• Project manager may never directly involved in producing the end product but he controls and manages the activities involved in production.
• A project manager closely monitors the development process, prepares and executes various plans, arranges necessary and adequate resources, maintains communication among all team members in order to address issues of cost, budget, resources, time, and quality and customer satisfaction.

Effective Software Project Management 4 P´s

1. People
2. Project
3. Product
4. Process

People

Mature resources, recruiting, selection, and performance.

GROW -> MOTIVATE -> RETAIN

Product

Before a Product can be planned, product objectives and scope should be established, alternative solutions should be considered and technical and management risks should be identified

OBJECTIVES -> SCOPE -> SOLUTIONS

Process

A number of different tasks, milestones, work

FRAMEWORK ACTS -> UMBRELLA ACTS -> QA POINTS

Project

Avoid a set of common warning signs

SUCCESS FACTORS -> SENSE APPROACH -> MONITORING PROJECT

What is Project Management?

Involves planning, monitoring, process, control of the people and events from a preliminary concept to an operational implementation. Everyone does it.

• Software Engineer: Manages day-to-day activities, planning, controlling and monitoring technical tasks
• Project Managers: Plan, monitor and control the work of a team of software engineers.
• Senior Managers: Coordinate the interface – communication between business and software professionals

How do I ensure that I’ve done it right?

Project manager does it right when he encourages software people to work together as an effective team, focusing their attention on customer needs and product quality.

Management Spectrum

• No success: The manager who forgets that software engineering is an intensive human endeavor
• Soft skills: The manager that fails to encourage comprehensive stakeholders communication
• Jeopardizes: The manager who embarks without a solid Project plan
• Risk and no elegant solution: The manager who pays little attention to the process runs

Software Management Activities

1. Project Planning: It is there for the software production but involves no concrete activity
2. Scope Management: This includes all the activities, process need to be done in order to make a deliverable software product.
3. Project Estimation: With correct estimation managers can manage and control the project more efficiently and effectively.

Milestones and Deliverables

Milestone is an end-point of a software activity. It could not be a formal output, such as report. It can indicate the completion of key project tasks, the commencement or conclusion of the plan.

[pic 1]

[pic 2]

Why is Project Scheduling important?

...