Syllabus

BCO232A Software Engineering and Project Management 3-0-0 [3]

Introduction- Introduction to Software Engineering, Software Components, Software Characteristics, Software Crisis,
UNIT 1 Engineering aspects of Software production – necessity of automation .Job responsibilities of Programmers and
Software Engineers as Software developers. Software Development Life Cycle (SDLC)
Process Models and Program Design Techniques- Software Development Process Models – Code & Fix model,
Waterfall model, Incremental model, Rapid Prototyping model, Spiral (Evolutionary) model. Software Requirement
UNIT 2 Specifications (SRS), Management of User Needs, Data Flow Diagrams, Entity Relationship Diagrams, Decision Tables,
SRS Document, Design Techniques – Structured Programming, Coupling and Cohesion, Abstraction and Information
Hiding, Software Modeling Tools –Data flow Diagrams, UML and XML.
Software Testing: Testing Objectives, Unit Testing, Integration Testing, Acceptance Testing, Regression Testing,
Verification and Validation: Testing of Software Products – Black-Box Testing and White-Box Testing, Static Analysis,
UNIT 3
Symbolic Execution and Control Flow Graphs –Cyclomatic Complexity. Maintainence and its need and types of
maintenance. CASE tools & graphical reporting tools.
Project Management: project, project specification parameters, principle &life cycle of project management, project
management Plan, why the project is delayed? and scheduling activities, Task Network & scheduling methods, critical
UNIT 4
Path, PERT& CPM. Effort Estimation Techniques Monitoring & Control: Change Control, Software Configuration
Management (SCM). Risk Analysis and Management, RMMM, Software Metrices.
Quality Management and People Management- Introduction, Understanding Behavior, Organizational Behavior,
Selecting The Right Person For The Job, Motivation, The Old man – Hackman Job Characteristics Model , Working in
Groups, Organization and team structures, Decision Making, Leadership, Organizational Structures, Stress, Health And
UNIT 5
Safety.

JECRC University 01-10-2022 08:56 2

 Mapping of CO with PO

Program
Course Program Outcome Specific
Outcome Outcome
PO1 PO2 PO3 PO4 PO5 PO6 PO7 PO8 PO9 PO10 PO11 PO12 PSO1 PSO2 PSO3

CO1 L H M L

CO2 H H M M

CO3 H M L H

CO4 L L L M L

JECRC University 01-10-2022 08:56 3

 SOFTWARE ENGINNERING

• Is the application of the systematic, disciplined and

quantifiable approach to the development
,operation and the maintenance of the software. It
encompasses techniques & procedures often
regulated by the system development process with
the purpose of improving reliability & the
maintenance.
 Need of Software Engineering

• Large software

• Scalability

• Cost

• Dynamic Nature

• Quality Management
 Characteristics of good software

A software product can be judged by what it offers

and how well it can be used. This software must
satisfy on the following grounds:
• Operational:- Budget, Usability, Efficiency, correctness,
functionality, dependability, safety & security.

• Transitional:- Portability, interoperability, reusability,

adaptability.

• Maintenance:- Modularity, Maintainability, Flexibility,

Scalability.
 SYSTEM ENGINEERING

• Systems engineering is an interdisciplinary field

of engineering and engineering management that focuses on how
to design, integrate, and manage complex systems over their life
cycles. ... Systems engineering deals with work-processes,
optimization methods, and risk management tools in such projects.

• Characteristics:- 1. Synergism

2. Adaptability

3. Compromise
 SOFTWARE CHARACTERISTICS

• Software is developed or engineered .It is not

manufactured in the classical sense.
Although some similarities exist b/w software
development & h/w development but the two activities
r different .
• Quality comes in terms of hardware and quality occurs
in terms of software.
SOFTWARE CHARACTERISTICS

• Software does not wear out but it does deteriorate.

• The relationship for software is called as “bathtub

curve”

• It indicates that h/w curve is spike curve.

SOFTWARE CHARACTERISITCS

• Although the industry is moving towards

component based construction ,most of the s/w
continues to be custom built.

• A software component should be designed &

implemented so that it can be reused in many
different programs.
SOFTWARE CHARACTERISITCS

1. Software does not wear out But it does deteriorate.

2. Software is not manufacture

3. Usability of Software

4. Reusability of components

5. Flexibility of software

6. Maintainability of software

7. Portability of software

8. Reliability of Software
 SOFTWARE CRISIS
• A set of problems encountered in the development of a
computer software.

• It is inability to develop a software on budget & within

requirement .

• Due to the lack of communication between the s/w & h/w.

• Increase in the cost of software as compared to the H/w.

• Lack of understanding of the problem & the environment .

• Cost & schedule are the major cause of S/w crisis.

 Cont…
• Software crisis explained as a mismatch in software
deliverables and the expectations a user have from the
computer system in terms of its capacity to work. Due to the
software crisis, programmers had to struggle always in order
to keep pace.

• The problems attached with low quality software like

inefficient software development, improper functioning of the
software systems along with the unhappiness within the
software users were the major causes for the software crisis
Job responsibilitie of a software developer

• Coordinate with the Technical Director on current programming tasks.

• Collaborate with other programmers to design and implement features.

• Quickly produce well-organized, optimized, and documented source code.

• Create and document software tools required by artists or other developers.

• Debug existing source code and polish feature sets.

• Contribute to technical design documentation.

• Work independently when required.

• Continuously learn and improve skills.

• Attention to detail is essential and all tasks must be carried out to the highest standard.
SDLC (Software Development Life Cycle)

SDLC stands for Software development life cycle. It is a process that

describes how to develop, design and maintain the software project
ensuring that all the functional & user requirement, goals and objective
are met. This methodology improves the quality of the software project
and over all process of software development.

Figure:- SDLC
 Phases of SDLC
• Requirement Analysis:- Explicit & implicit s/w
requirement specification obtained by studying problem domain,
operational timelines and procedure environment.

SRS is prepared in this phase only.

• Design Specification:- Software development

plan,implicit and explicit Software requirement and the software
architecture.

• INTERNAL DESIGN: Algorithm& pseudo code

• EXTERNAL DESIGN: User interface.H/w interface, global and

control structure.
 Cont…
• Development:- This is the longest phase of
SDLC as in this phase of SDLC actual project is
developed and build. This phase of SDLC includes:-
• Actual code gets written.
• Demonstration of work accomplished to Business
analyst for future modification as per requirement.
• Unit testing is performed i.e. verification of code as
per requirements.
 Cont…

• Testing:- The testing strategy is involved in almost all stages of

SDLC. However this phase of SDLC refers to the only testing of
system where bugs/defect of the system are reported, tracked and
fixed. The system/project is migrated to a test environment and
different type of testing is performed like functional, integration, system
and acceptance. This is performed until the project reaches the quality
standards as specified in SRS. This phase of SDLC includes:-

• System is tested as a whole

• Different type of testing to report & fix bugs.

 Cont…

• Deploy & Maintenance:- In this phase of SDLC, once the

system is tested, it is ready to go live. The system may be first released
for limited user, and tested in real business environment for UAT (user
acceptance testing).This phase of SDLC includes:-

• System is ready to be delivered.

• System is installed and put into use.

• Correction of errors that were not caught before.

• Improving system and ultimately enhanced system in data center.