Introduction
Intro 2
Medyo Module 2
Module 2
Module 2 parin kase bobo ka
100

Computer science is still a young field. The first

computers were built in

the mid 1940s

100

A model of the whole system is

developed which, when encoded in some programming

language, solves the problem for the user.

Design

100

An important activity not identified separately is _______. Since many projects are pressed for time, the ________ tends to get the worst of it. However, it is important to realize that software which is not sufficiently documented is bound to incur high costs later on.

Documentation

100

Need of software project management

Time, Cost, Quality

100

It is performed before the production of software actually starts.

Project Planning


200

The time when people started to realize that programming

techniques had lagged behind the developments in

software both in size and complexity.

1960s

200

After delivery of the software, there are often errors that have still gone undetected.,

Obviously, these errors must be repaired. In addition, the actual use of the system can lead

to requests for changes and enhancements.

Maitenance

200

The _______________ should be task-oriented in the sense that the

software to be delivered should support users in their task environment.

Likewise, the user documentation should be task-oriented

Software development

200

A person who undertakes the responsibility of executing the software project. He/she is thoroughly aware of all the phases of SDLC that the software would go through.

Software Project Manager

200

It defines the scope of project; this includes all the activities, process need to be done in order to make a deliverable software product. ______________ is essential because it creates boundaries of the project by clearly defining what would be done in the project and what would not be done.

Scope Management

300

The application of a

systematic, disciplined, quantifiable approach to

the development, operation, and maintenance of

software; that is, the application of engineering to

software

Software engineering

300

It is wrong to say that ______ is a phase following

implementation. This suggests that you need not bother about this phase until implementation is finished. This is not true. It is even fair to say that

this is one of the biggest mistakes you can make.

Testing

300

4 kinds of Maintenance activities

•Corrective maintenance

•Adaptive maintenance

•Perfective maintenance

•Preventive maintenance

300

4 types of managing people:

Clue: ALMS

Managing People

•Act as project leader

•Liaison with stakeholders

•Managing human resources

•Setting up reporting hierarchy etc.

300

For an effective management accurate estimation of various measures is a must. With correct estimation managers can manage and control the project more efficiently and effectively.

Project Estimation


400

This concerns the

construction of large programs.

Software engineering

400

A kind of programming language. Its syntax and semantics

are in general less strict, so that algorithms can be formulated at a higher,

more abstract, level.

Pseudocode


400

The job pattern of an IT company engaged in software

development can be seen split in two parts. Ano yung mga yun?

•Software Creation

•Software Project Management

400

6 activities in managing project.

Clue: DMMRTA

Managing Project

•Defining and setting up project scope

•Managing project management activities

•Monitoring progress and performance

•Risk analysis at every phase

•Take necessary step to avoid or come out of problems

•Act as project spokesperson

400

4 types of Project Estimation.

Clue: SETC


• Software size estimation

• Effort estimation

• Time estimation

• Cost estimation

500

The goal of this phase is to get a complete description of the

problem to be solved and the requirements posed by and on the environment in which the

system is going to function.

Requirements engineering

500

During this phase, we concentrate on the individual

modules. Our starting point is the module's specification. It is often

necessary to introduce an extra 'design' phase, the step from module

specification to executable code often being too large. In such cases, we may

take advantage of some high-level, programming-language-like notation,

such as a pseudocode.

Implementation

500

The complete procedure of software development from requirement gathering to testing and maintenance, carried out according to the execution methodologies, in a specified period of time to achieve intended software product.

Software Project

500

3 Software Management Activities

Clue: PSP


•Project Planning

•Scope Management

•Project Estimation

500

1. This technique assumes the software as a product of various compositions. 

2. Estimation is done on behalf of number of line of

codes in the software product.

3. Estimation is done on behalf of number of function points in the software product.

1. Decomposition Technique

2. Line of code
3. Function points

M
e
n
u