0% found this document useful (0 votes)
21 views9 pages

Software

The document discusses a lab assignment on software engineering. It includes details about the course objectives and outcomes. It also outlines the experiments to be performed, which involve explaining the software development life cycle, comparing different models, identifying problem statements and requirements, creating a synopsis, and modeling diagrams.

Uploaded by

Somesh Shukla
Copyright
© © All Rights Reserved
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% found this document useful (0 votes)
21 views9 pages

Software

The document discusses a lab assignment on software engineering. It includes details about the course objectives and outcomes. It also outlines the experiments to be performed, which involve explaining the software development life cycle, comparing different models, identifying problem statements and requirements, creating a synopsis, and modeling diagrams.

Uploaded by

Somesh Shukla
Copyright
© © All Rights Reserved
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/ 9

[68_1345_ Startup-AYUSH Portal] [2024]

Acropolis Institute of Technology and


Research, Indore
Department of Computer Science and Engineering

B. Tech. IV Semester

Jan - June 2024


Lab Assignment
On
Software Engineering [CS 403]

Submitted To: Submitted By:


Prof. Sushma Khatri Somesh Shukla
Senior Assistant Professor
(0827CS221268)

[CS4 II Year_0827CS221268]
[68_1345_ Startup-AYUSH Portal] [2024]
Course Educational Objectives

CEO1 Understand the basics of software development life cycle as a product.

CEO2 Understand the current requirements of industries for software standards


CEO3 Implement the software as a product using different design patterns
CEO4 Apply the software development techniques in real life applications.
Understand the existing software solutions and correlate with the SDLC,
CEO5
design patterns and software standards

Course Outcomes
Upon completion of this subject / course the student will be able:

Specify, classify, implement, analyze and develop applications using


CO1
various SDLC models like Linear sequential, prototype, Evolutionary models
Understand, classify, analyze and develop applications using Various
CO2
software standards. .
Understand, classify, implement various types of design patterns
CO3 (Creational, Behavioral, structural); understand and analyze each design
pattern using java program
Understand, classify, implement various types of design patterns
CO4 (Presentation layer, Integration layer, business layer ); Analyze the problem
statement make UML diagram and code the program in java .
Able to describe the SDLC, design patterns and software standards
CO5
applicable to the existing software systems.

[CS4 II Year_0827CS221268]
[68_1345_ Startup-AYUSH Portal] [2024]

TABLE OF CONTENTS
S. TOPIC PAGE Date of Date of REMARK
NO. NO Experiment Submission
1. EXPLAIN SDLC IN DETAIL.
(HANDWRITTEN)
2. COMPARE FOLLOWING MODELS:
(HANDWRITTEN)
A. LINEARSEQUENTIAL MODEL,
B. PROTOTYPING MODEL,
C. RAD MODEL,
EVOLUTIONARY PROCESS
MODELS LIKE
D. INCREMENTAL MODEL,
E. SPIRAL MODEL,
F. COMPONENT ASSEMBLY
MODEL,
G. RUP AND
H. AGILEPROCESSES
I. CMM
POINT FOR COMPARISON:
A. YEAR
B. PROPOSED BY
C. DIAGRAM
D. BRIEF DESCRIPTION
E. ADVANTAGES
F. DISADVANTAGES
G. WHEN BEST SUITED
3. PROBLEM STATEMENTS :
IDENTIFYING THE
REQUIREMENTS
4. SYNOPSIS

5. ESTIMATION OF PROJECT
METRICS
6. MODELING UML USE CASE
DIAGRAMS
7. MODELING DATA FLOW
DIAGRAMS
8. E-R MODELING FROM THE

[CS4 II Year_0827CS221268]
[68_1345_ Startup-AYUSH Portal] [2024]

PROBLEM STATEMENTS

9. IDENTIFYING DOMAIN CLASSES


FROM THE PROBLEM
STATEMENTS
10. STATE TRANSITION DIAGRAM

11. STATECHART AND ACTIVITY


MODELING
12. MODELING UML CLASS
DIAGRAMS
13. MODELING UML SEQUENCE
DIAGRAMS
14. ESTIMATION OF TEST COVERAGE
METRICS AND STRUCTURAL
COMPLEXITY
15. DESIGNING TEST SUITES

16. SOFTWARE REQUIREMENT


SPECIFICATION (SRS)

[CS4 II Year_0827CS221268]
[68_1345_ Startup-AYUSH Portal] [2024]

Experiment I
EXPLAIN SDLC IN DETAIL (HANDWRITTEN)

[CS4 II Year_0827CS221268]
[68_1345_ Startup-AYUSH Portal] [2024]

Experiment II
COMPARE FOLLOWING MODELS: (HANDWRITTEN)
1. LINEARSEQUENTIAL MODEL,
2. PROTOTYPING MODEL,
3. RAD MODEL,
EVOLUTIONARY PROCESS MODELS LIKE
4. INCREMENTAL MODEL,
5. SPIRAL MODEL,
6. COMPONENT ASSEMBLY MODEL,
7. RUP AND
8. AGILEPROCESSES
9. CMM
POINT FOR COMPARISON:
A. YEAR
B. PROPOSED BY
C. DIAGRAM
D. BRIEF DESCRIPTION
E. ADVANTAGES
F. DISADVANTAGES
G. WHEN BEST SUITED

[CS4 II Year_0827CS221268]
[68_1345_ Startup-AYUSH Portal] [2024]

Experiment III
PROBLEM STATEMENT: IDENTIFYING THE REQUIREMENTS
1. Problem Statement
Detailed description of the problem that you are solving.

2. Solution Proposed
Detailed solution of the problem

3. Users
Detailed description of each user.

4. Functionalities
Identification of functional requirements.
 Function1
 Function2
…..

Table 01: Identifier and priority for software requirements


# Requirement Priority
R1
R2

Identification of non-functional requirements.

[CS4 II Year_0827CS221268]
[68_1345_ Startup-AYUSH Portal] [2024]

Experiment II
Synopsis
1. Abstract
A very short gist of the problem addressed.

2. Introduction of the Project (1 paragraph)


A brief introduction about the project should be given in this section. This section consists what is
the project all about? Describe the rational and what could be the probable problems that would be
addressed during the course of project?

3. Objective (100 words)


Statements which directly state what has to be done for addressing the problem stated. Objective
should be clearly specified. What the project ends up to and in what way this is going to help the
end user should be mentioned specifically.

4. Scope (100 words)


This should clearly mention the scope and intended audience where the project is applicable.

5. Study of Existing System (200 words)


A case study of at least 5 existing systems should be done and relative comparison with their merits
and demerits. This will help in formulation of further objectives that could be addressed within the
project.

 Existing System/Application 1:
o Problems Addressed
o Advantages
o Disadvantages
o Gaps Identified
o Reference link

 Existing System/Application 2:
o Problems Addressed
o Advantages
o Disadvantages
o Gaps Identified
o Reference link

 Existing System/Application 3:
o Problems Addressed
o Advantages
o Disadvantages
o Gaps Identified
o Reference link

[CS4 II Year_0827CS221268]
[68_1345_ Startup-AYUSH Portal] [2024]
 Existing System/Application 4:
o Problems Addressed
o Advantages
o Disadvantages
o Gaps Identified
Reference link

 Existing System/Application 5:
o Problems Addressed
o Advantages
o Disadvantages
o Gaps Identified
Reference link

6. Project Description (200 words)


The process of the whole software system proposed, to be developed, should be mentioned in brief.
This may be supported by Flowcharts/ER diagram to explain the flow of the information.

7. Methodology/Planning of the Project work (200 words)


Methodology includes the steps to be followed to achieve the objective of the project during the
project development.

8. Expected Outcome (100-150 words)


Briefly illustrate the outcomes of the project development along with the benefits to the society.

9. Resources and Limitations (150 words)


The requirement of the resources for designing and developing the proposed system must be given.
The resources might be in form of the hardware / software or the data from the industry. The
limitations of the proposed system in respect of a larger and comprehensive system must be given.

10.Conclusion (100-150 words)


The write-up must end up with the concluding remarks-briefly.

11.References
Mention the sources referred for the study and development of the project. References include
literature, books, websites or any other kind of resource directly or indirectly referred for
development of project and its report. All the references should be listed in IEEE format.

[CS4 II Year_0827CS221268]

You might also like