SOFTWARE ENGINEERING WITH AGILE METHODOLOGY LABORATORY -1-

LABORATORY MANUAL

SOFTWARE ENGINEERING
WITH AGILE
&
METHODOLOGY
(AD 403)

IV Semester (AI&DS)

CHAMELI DEVI GROUP OF

INSTITUTIONS, INDORE

CHAMELI DEVI GROUP OF INSTITUTIONS, INDORE DEPARTMENT OF AI&DS

SOFTWARE ENGINEERING WITH AGILE METHODOLOGY LABORATORY -2-

CHAMELI DEVI GROUP OF INSTITUTIONS

INDORE (M.P.)

DEPARTMENT OF
Artificial Intelligence & Data Science

CERTIFICATE

This is to certify that Mr./Ms……………………………………………………………… with RGTU

Enrollment No. 0832 ..…………………………..has satisfactorily completed the course of experiments in

Software Engineering with Agile Methodology laboratory, as prescribed by Rajiv Gandhi Proudhyogiki

Vishwavidhyalaya, Bhopal for IV Semester of the AI&DS Department during year 2022-23

Signature of
Faculty In-charge

CHAMELI DEVI GROUP OF INSTITUTIONS, INDORE DEPARTMENT OF AI&DS

SOFTWARE ENGINEERING WITH AGILE METHODOLOGY LABORATORY -3-

INDEX

Sl. Expt. Name of the Experiment Date of Signature

No. No. Conduction of Faculty-
in-Charge
Develop Software Requirement Specification for Library
1 1 Management System

Case Study Of Waterfall Model & Spiral Model-

2 2

Case Study of RAD Model

3 3

Case Study of Agile Methodology Model

4 4

Study and usage of any Design phase CASE tool

5 5
Design .USE Case & Class diagram for Library Management
6 6
System
Draw Activity Diagram for Employee Management System.
7 7 sequence diagram for Online Exam System

Draw a DFD Diagram For Online Shopping System

8 8

Develop test cases for various white box and black box testing
9 9 techniques

Studies about the Software Cost Estimation Model

10 10

CHAMELI DEVI GROUP OF INSTITUTIONS, INDORE DEPARTMENT OF AI&DS

SOFTWARE ENGINEERING WITH AGILE METHODOLOGY LABORATORY -4-
EXPT. No. – 1. Develop Software Requirement Specification for Library Management System

Aim: Develop Software Requirement Specification for Library Management System

Theory:
Software Requirement Specification (SRS) document usually contains a software vendor understanding of a
customer software requirement. It is created after the initial requirement elicitation phase in which software
vendor interacts with the customer to understand the software needs. Usually, SRS documentation is
prepared by a business analyst who has some technical background.
Functional Requirements
Functional requirements specify the business requirements of the project in detail. Usually, business
requirements are specified in terms of the actions that user performs on the software system. This is known as
the use case model. But not all requirements need to be specified as use cases. Functional requirements
should contain a combination of use cases and plain textual description of system features. System features
are specified at a higher level and use cases attempt to translate into user actions. There is no fixed format for
use case description, but it usually contains the following information.
 Use case diagram – For a small system, a single diagram can be used to depict all the use cases in the
system.
 List of actors and their details – This identifies the various types of users interacting with the software
system.
 Use case description – Purpose of the use case and how and when it is invoked by the user. This should
also include an identifier for easy reference.
 Preconditions – List of system states/conditions that must be true for the successful execution of the
use case. This section is optional and could be easily incorporated into the basic steps section.
 Basic steps – These indicates the various fine-grained steps required for the execution of the use case.
 Alternate steps – These indicate alternate events of the use case being described.
 Business validations/rules – These indicates various types of input validations or business rules
required in the use case being described.
 Post conditions – Indicates the results of the use case.

Library Management System: A library management system, also known as an automated library system is
software that has been developed to handle basic housekeeping functions of a library.
 It is a well-organized software solution for a library.
 It helps to provide information on any book present in library to the user as well as staff member.
 It keeps a track of book issued, returned and added to library.

CHAMELI DEVI GROUP OF INSTITUTIONS, INDORE DEPARTMENT OF AI&DS

SOFTWARE ENGINEERING WITH AGILE METHODOLOGY LABORATORY -5-

Viva Question:
1. What is functional and non-functional requirement?
2. What do you understand by data dictionary?
3. What is the requirement of SRS?
4. Explain the characteristics of SRS.
5. Define types of requirements.

EXPT. No. - 2. Case Study Of Waterfall Model & Spiral Model

Aim: Case Study Of Waterfall Model & Spiral Model

Theory:

Waterfall Model

Waterfall approach was first SDLC Model to be used widely in Software Engineering to ensure success of the
project. In "The Waterfall" approach, the whole process of software development is divided into separate
phases. In this Waterfall model, typically, the outcome of one phase acts as the input for the next phase
sequentially.

 Requirement Gathering and analysis − All possible requirements of the system to be developed are
captured in this phase and documented in a requirement specification document.
 System Design − The requirement specifications from first phase are studied in this phase and the
system design is prepared. This system design helps in specifying hardware and system requirements and
helps in defining the overall system architecture.
 Implementation − With inputs from the system design, the system is first developed in small programs
called units, which are integrated in the next phase. Each unit is developed and tested for its
functionality, which is referred to as Unit Testing.

CHAMELI DEVI GROUP OF INSTITUTIONS, INDORE DEPARTMENT OF AI&DS

SOFTWARE ENGINEERING WITH AGILE METHODOLOGY LABORATORY -6-
 Integration and Testing − All the units developed in the implementation phase are integrated into a
system after testing of each unit. Post integration the entire system is tested for any faults and failures.
 Deployment of system − Once the functional and non-functional testing is done; the product is
deployed in the customer environment or released into the market.
 Maintenance- There are some issues which come up in the client environment. To fix those issues,
patches are released. Also to enhance the product some better versions are released. Maintenance is done
to deliver these changes in the customer environment.

Spiral model
Spiral model is one of the most important Software Development Life Cycle models, which provides
support for Risk Handling. In its diagrammatic representation, it looks like a spiral with many loops.
As the project manager dynamically determines the number of phases, so the project manager has an
important role to develop a product using the spiral model.

Objectives determination and identify alternative solutions:

Requirements are gathered from the customers and the objectives are identified, elaborated, and
analyzed at the start of every phase. Then alternative solutions possible for the phase are proposed in
this quadrant.
Identify and resolve Risks:
During the second quadrant, all the possible solutions are evaluated to select the best possible
solution. Then the risks associated with that solution are identified and the risks are resolved using the
best possible strategy. At the end of this quadrant, the Prototype is built for the best possible solution.
Develop next version of the Product
During the third quadrant, the identified features are developed and verified through testing. At the
end of the third quadrant, the next version of the software is available.
Review and plan for the next Phase:
In the fourth quadrant, the Customers evaluate the so far developed version of the software. In the
end, planning for the next phase is started.

CHAMELI DEVI GROUP OF INSTITUTIONS, INDORE DEPARTMENT OF AI&DS

SOFTWARE ENGINEERING WITH AGILE METHODOLOGY LABORATORY -7-
Viva Question:
1. What is Waterfall Model?
2. Identify the steps of Waterfall model?
3. Difference Between Waterfall and spiral Model?
4. What do you mean by Spiral Model
5. Explain phases of Spiral Model

EXPT. No. – 3. Case Study of RAD Model

Aim: Case Study of RAD Model

Theory:

The RAD (Rapid Application Development) model is based on prototyping and iterative development
with no specific planning involved. The process of writing the software itself involves the planning
required for developing the product.
• In the RAD model, the functional modules are developed in parallel as prototypes and are integrated to
make the complete product for faster product delivery. Since there is no detailed preplanning, it makes
it easier to incorporate the changes within the development process.

• The business model for the product under development is designed in terms of flow of information and
the distribution of information between various business channels. A complete business analysis is
performed to find the vital information for business, how it can be obtained, how and when is the
information processed and what are the factors driving successful flow of information.

• The information gathered in the Business Modelling phase is reviewed and analyzed to form sets of
data objects vital for the business. The attributes of all data sets is identified and defined. The relation
between these data objects are established and defined in detail in relevance to the business model.

• The data object sets defined in the Data Modelling phase are converted to establish the business
information flow needed to achieve specific business objectives as per the business model. The process

CHAMELI DEVI GROUP OF INSTITUTIONS, INDORE DEPARTMENT OF AI&DS

SOFTWARE ENGINEERING WITH AGILE METHODOLOGY LABORATORY -8-
model for any changes or enhancements to the data object sets is defined in this phase. Process
descriptions for adding, deleting, retrieving or modifying a data object are given.

• The actual system is built and coding is done by using automation tools to convert process and data
models into actual prototypes.

• The overall testing time is reduced in the RAD model as the prototypes are independently tested
during every iteration. However, the data flow and the interfaces between all the components need to
be thoroughly tested with complete test coverage. Since most of the programming components have
already been tested, it reduces the risk of any major issues.

Viva Question:
1. What is RAD Model
2. Explain Phases of RAD Model?
3. What is the main purpose of using RAD Model?
4. How it is Differe from Spiral Model
5. Explain advantages and Disadvantages Of RAD Model

CHAMELI DEVI GROUP OF INSTITUTIONS, INDORE DEPARTMENT OF AI&DS

SOFTWARE ENGINEERING WITH AGILE METHODOLOGY LABORATORY -9-

EXPT. No. –4. Case Study of Agile Methodology Model

Aim: Case Study of Agile Methodology Model

Theory:

The meaning of Agile is swift or versatile."Agile process model" refers to a software development
approach based on iterative development. Agile methods break tasks into smaller iterations, or parts
do not directly involve long term planning. The project scope and requirements are laid down at the
beginning of the development process. Plans regarding the number of iterations, the duration and
the scope of each iteration are clearly defined in advance.

1. Requirements gathering: In this phase, you must define the requirements. You should explain
business opportunities and plan the time and effort needed to build the project. Based on this
information, you can evaluate technical and economic feasibility.

2. Design the requirements: When you have identified the project, work with stakeholders to
define requirements. You can use the user flow diagram or the high-level UML diagram to show
the work of new features and show how it will apply to your existing system.

3. Construction/ iteration: When the team defines the requirements, the work begins.
Designers and developers start working on their project, which aims to deploy a working
product. The product will undergo various stages of improvement, so it includes simple,
minimal functionality.

4. Testing: In this phase, the Quality Assurance team examines the product's performance and
looks for the bug.

5. Deployment: In this phase, the team issues a product for the user's work environment.

6. Feedback: After releasing the product, the last step is feedback. In this, the team receives
feedback about the product and works through the feedback

CHAMELI DEVI GROUP OF INSTITUTIONS, INDORE DEPARTMENT OF AI&DS

SOFTWARE ENGINEERING WITH AGILE METHODOLOGY LABORATORY - 10 -
Viva Question:
1. What is Agile Process
2. Explain Phases of Agile Model?
3. How it is different from SDLC Model
4. What is Purspose Of Using Agile Process Model
5. Explain advantages and Disadvantages Of Agile Model

EXPT. No. - 5. Study and usage of any Design phase CASE tool

Aim: . Study and usage of any Design phase CASE tool

Theory:

How to Install StarUML on Windows 10 Star UML is a UML (Unified Modeling Language) tool, introduce by
MKLab. It is an open-source modeling tool that supports the UML framework for system and software
modeling. StarUML is based on UML version 1.4, it provides 11 different types of diagram and it accepts UML
2.0 notation. Version 2.0 was released for beta testing under a property license. StarUML is actively supporting
the MDA (Model Driven Architecture). It approaches by supporting the UML profile concept and allowing it to
generate code for multiple languages. It also provides a number of bug fixes and improved compatibility with
the modern versions of the Windows Operating System.

StarUML is mostly used by the Agile and small development teams, professional persons and used by the
educational institutes

Diagram Types in StarUML

1. Use Case Diagram
2.Class Diagram
3.Sequence Diagram
4.Collaboration Diagram
5.Statechart Diagram
6.Component Diagram
7.Deployment Diagram
8.Composite Structure Diagram

Features of StarUML
1. It supports multi-platform such as macOS, Windows, and Linux.
2. It involves UML 2.x.standard compliant.
3. Includes Entity-Relationship diagram (ERD), Data-flow diagram (DFD), and Flowchart diagram
. 4. It creates multiple windows.
5. It has modern UX and dark and light themes.
6. Featured with retina (High-DPI) display support.
CHAMELI DEVI GROUP OF INSTITUTIONS, INDORE DEPARTMENT OF AI&DS
SOFTWARE ENGINEERING WITH AGILE METHODOLOGY LABORATORY - 11 -
7. Includes model-driven development.
8. It has open APIs.
9. Supports various third-party extensions.
10. Asynchronous model validation
11. It can export to HTML docs.

Steps to Download and Install StarUML Step

1: Go on the browser, type in the URL “StarUML”
Step 2: Click on the very first search “Download-StarUML”.
Step 3: There will be 3 Operating Systems (OS) options, click on the option as per the devise OS.
Step 4: Now, right-click on the downloaded file, select “Show in Folder” option.
Step 5: Click on the open file, a popup window opens, click on the “Yes” button.
Step 6: Installation gets start. After installation popup opens to ask to buy a license. If you want to click on the
“Buy Now” button or else close that window. StarUML is ready to use

Viva Question:
1. What is Star UML?
2. How to Install Star UML?
3. What is the main purpose of using Star UML?
4. Which Type of Diagram are used in Star UML
5. Explain its Charecterstics.

CHAMELI DEVI GROUP OF INSTITUTIONS, INDORE DEPARTMENT OF AI&DS