Ujjain Engineering College: Department of Computer Science and Engineering

UJJAIN ENGINEERING COLLEGE
DEPARTMENT OF
COMPUTER SCIENCE AND ENGINEERING
Academic Year: 2021-2022
Submitted To:- Assistant Professor Rahul Sharma Submitted By :- VIVEK AJMERI

Department of Computer Science and Engineering Rollno :- 0701CS181059
(Software Engineering and Project Managment) Branch:- Computer Science and Engineering
Year:- 3rd year, 5th semester
Department Computer Science and Engineering 1

Submitted By :- Vivek Ajmeri
Roll no :- 0701CS181059
Experiment 1
Aim:- Introduction to software engineering and

program managment and also describe the
SDLC(software development life cycle).
Theory:-
1 Software Engineering and Project Managment
Software is a term referred to a set of instructions which
when executed provide a desired functionality. Software
engineering is a engineering branch associated with
development of software product using well defined methods
and principles. Utilization on SEPM model makes the
developed software effective and reliable software product.
Software Managment go in hand to hand with Software

Engineering. Software managment is the domain of pre and
post release support of communication, maintainance and
update.
Use of a proper development methodology makes a program

1 Portable
2 Adaptable
3 Reusable
4 Testable
5 Reliable
6 Operationally correct
7 Maintainable
2 SDLC(Software Development Life Cycle

Submitted By:- Vivek Ajmeri
Rollno:- 0701CS181059
Software Development Life Cycle is a process of requirement
gathering, designing, developing, testing and mentaining.
Therefore it is also called Software Process Model.
Types of Software Development Models:-

1 Prescriptive Modeling
2 Evolutionary Modeling
3 Agile Modeling
1. Prescriptive Modeling:-
Prescriptive modeling prescribes a set of activities,
actions, tasks, quality assurance and change the mechanism
for every project.
For every sub type of prescriptive modeling the set of
requirement is fixed.
I. The Waterfall Model.

Waterfall model was the first Process Model to be introduced
hence it is a Base Model. It is also referred to as a Linear

Rollno:- 0701CS181059
Sequential Life Cycle Model. It is very simple to understand
and use. In a waterfall model, each phase must be completed
before the next phase can begin and there is no overlapping
in the phases.
In waterfall model any phase in the development process begin
only if the previous phase is complete. In Waterfall model,
the phase do not overlap.
Water Fall Model Graphical Representation

Requirement Gathering:- All possible requirements of the
system to be developed are captured in this phase and
documented in a requirement specification document called
SRS.
Designing:- 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. This phase results in formation of doument
called as design defination specification also known as DDS.

Rollno:- 0701CS181059
Coding:- 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.
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.
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.
All these phases cascaded to each other. In this method the

property of phases feedback is not avilable, therefore
backtracing is alien to waterfall modeling.
Advantages:-
1. Easy to maintain.
2. Easy Modeling.
3. Low costing while using this model.
4. Good for small program develpment.
Disadvantages:-
1. Risk is high(of failure).
2. Can’t change your requirements once they are fixed.
3. No backtracking allowed.
4. Overlapping is also not allowed.

Rollno:- 0701CS181059
2. Evolutionary
I. Prototype Modeling.
Prototyping is defined as the process of developing a working
replication of a product or system that has to be engineered.
It offers a small scale facsimile of the end product and is
used for obtaining customer feedback.
Prototype Modeling
Advantages.
1. The customers get to see the partial product early in the
life cycle. This ensures a greater level of customer
satisfaction and comfort.
2. New requirements can be easily accommodated as there is
scope for refinement.
3. Missing functionalities can be easily figured out.
4. Errors can be detected much earlier thereby saving a lot of
effort and cost, besides enhancing the quality of the
software.
5. The developed prototype can be reused by the developer for
more complicated projects in the future.
6. Flexibility in design.
Disadvantages.

Rollno:- 0701CS181059
1. Costly w.r.t time as well as money.
2. There may be too much variation in requirements each time
the prototype is evaluated by the customer.
3. Poor Documentation due to continuously changing customer
requirements.
4. It is very difficult for developers to accommodate all the
changes demanded by the customer.
5. There is uncertainty in determining the number of
iterations that would be required before the prototype is
finally accepted by the customer.
6. After seeing an early prototype, the customers sometimes
demand the actual product to be delivered soon.
7. Developers in a hurry to build prototypes may end up with
sub-optimal solutions.
8. The customer might lose interest in the product if he/she
is not satisfied with the initial prototype.
3. Agile Modeling.
Agile model believes that every project needs to be handled
differently and the existing methods need to be tailored to best
suit the project requirements. In Agile, the tasks are divided
to time boxes (small time frames) to deliver specific features
for a release.
Iterative approach is taken and working software build is
delivered after each iteration. Each build is incremental in
terms of features; the final build holds all the features
required by the customer.

Rollno:- 0701CS181059
Agile Model
Agile Vs Traditional SDLC Models:
Agile is based on the adaptive software development methods,
whereas the traditional SDLC models like the waterfall model is
based on a predictive approach. Predictive teams in the
traditional SDLC models usually work with detailed planning and
have a complete forecast of the exact tasks and features to be
delivered in the next few months or during the product life
cycle.
Predictive methods entirely depend on the requirement analysis
and planning done in the beginning of cycle. Any changes to be
incorporated go through a strict change control management and
prioritization.
Agile uses an adaptive approach where there is no detailed
planning and there is clarity on future tasks only in respect of
what features need to be developed. There is feature driven
development and the team adapts to the changing product

Rollno:- 0701CS181059
requirements dynamically. The product is tested very frequently,
through the release iterations, minimizing the risk of any major
failures in future.
Customer Interaction is the backbone of this Agile methodology,
and open communication with minimum documentation are the
typical features of Agile development environment. The agile
teams work in close collaboration with each other and are most
often located in the same geographical location.
Advantages:−
1. Is a very realistic approach to software development.
2. Promotes teamwork and cross training.
3. Functionality can be developed rapidly and demonstrated.
4. Resource requirements are minimum.
5. Suitable for fixed or changing requirements
6. Delivers early partial working solutions.
7. Good model for environments that change steadily.
8. Minimal rules, documentation easily employed.
9. Enables concurrent development and delivery within an
overall planned context.
10. Little or no planning required.
11. Easy to manage.
12. Gives flexibility to developers.
Disadvantages:−
1. Not suitable for handling complex dependencies.
2. More risk of sustainability, maintainability and
extensibility.
3. An overall plan, an agile leader and agile PM practice is a
must without which it will not work.
4. Strict delivery management dictates the scope,
functionality to be delivered, and adjustments to meet the
deadlines.

Rollno:- 0701CS181059
5. Depends heavily on customer interaction, so if customer is
not clear, team can be driven in the wrong direction.
6. There is a very high individual dependency, since there is
minimum documentation generated.
7. Transfer of technology to new team members may be quite
challenging due to lack of documentation.
Result:- Hence we have learned about the Software Development and

project managment and the SDLC under SEPM.

Rollno:- 0701CS181059
Experiment 2
Aim:- Development of Software Requirement Specification

document and Design Defination Specification for the
sample Project.
SRS
Theory :-
A software requirements specification is the basis for your
entire project. It lays the framework that every team involved
in development will follow. It’s used to provide critical
information to multiple teams development, quality assurance,
operations, and maintenance. This keeps everyone on the same
page. Using the SRS helps to ensure requirements are fulfilled.
And it can also help you make decisions about your product’s
lifecycle for instance, when to retire a feature. Writing an SRS
can also minimize overall development time and costs. Embedded
development teams especially benefit from using an SRS.
Project Plan: MeetUrMate

1. Introduction
This document lays out a project plan for the development of the
“MeetUrMate” open source repository system by Anurag Mishra.
The intended readers of this document are current and future
developers working on “MeetUrMate” and the sponsors of the
project. The plan will include, but is not restricted to, a
summary of the system functionality, the scope of the project
from the perspective of the “MeetUrMate” team (me and my
mentors), scheduling and delivery estimates, project risks, and
how those risks will be mitigated, the process by which I will
develop the project, and metrics and measurements that will be
recorded throughout the project.

Rollno:- 0701CS181059
2. Overview
In today’s world, owning to the heavy workload on the employees,
they are having a huge amount of stress in their lives. Even
with the presence of so many gadgets in and around them, they
are not able to relieve their stress. I aim to develop an
application that would enable them to share the thing of their
liking and meet the person who has the same passion as theirs.
For eg. If someone wants to share their art, they can share it
through the platform, if someone wants to sing any song, they
can record it and share the same. They can also share videos
(with some funny commentary in the background), share mysteries
which other people can solve, post any question. Through my
platform, I’ll enable them to meet people who share common
interests and passions, chat with them, and have some fun.
2.1 Customers
Everyone. Anyone can use this application ranging from a child
to an old-age person.
2.2 Functionality
• Users should be able to register through their already
existing accounts.
• They should be able to share snaps/videos/snaps.
• People should be able to like and comment on any post. One
person can follow another person who shares common
interests and likings which would enable them to find mates
apart from their usual friend circle.
• Each user can have his/her profile picture, status
• People can post mysteries and other people can solve the
mysteries.
• Users will get points for the popularity of their posts/the
number of mysteries they solve.
• Add own funny commentary on any video
• Post any questions regarding their interests and people can
answer.
2.3 Platform
It will be launched both as a Web-based application and a Mobile
app for Android.

Rollno:- 0701CS181059
2.4 Development Responsibility
I, Anurag Mishra, would be developing the software and I am
responsible for the creation of the Database and all the other
related kinds of stuff.
3. Goals and Scopes
• Users should be able to register through their already
existing accounts.
• They should be able to share snaps/videos/snaps.
• People should be able to like and comment on any post.
• One person can follow another person who shares common
interests and likings which would enable them to find mates
apart from their usual friend circle.
• Each user can have his/her profile picture, status.
• People can post mysteries and other people can solve the
mysteries.
• Users will get points for the popularity of their posts/the
number of mysteries they solve.
4. Deliverables
I’ll deliver the following during the course of development:
• Feature specification
• Product design
• Test plan
• Development document
• Source code
5. Risk Management
5.1 Risk Identification
Following will be the risk involved in my project:
1) People are already using Facebook to find friends. So, what
would be the real cause that would motivate them to join my
application?
5.2 Risk Mitigation
Even though most of the users would already be using Facebook,
our platform would still offer them many things that are not
there on Facebook. For eg.

Rollno:- 0701CS181059
1.They don’t meet people who share common interests and
passions as much. Our application would enable them to meet
people (apart from usual friends) who share common
interests and passions on a more frequent basis.
2.Users of FB cannot share songs on-the-go which they have
sung whereas on our app they can do that on the go.
3.People can post mysteries/cases and other people can solve
them. Moreover, people will get points in case they solve
the mysteries or on the basis of the popularity of their
posts.
4.More importantly, people need not register for my
application, but instead, they can log in using their
already existing accounts of Google/Facebook.
Thus, I think that there is a considerable amount of difference
between Facebook/Instagram/Twitter and my application and it
would attract many people.
6. Scheduling and Estimates
Milestone Description Release Date Release
Iteration
Application view October 5,
M1 R1
and Design 2015
(Front-end
development)
Database for my October 17,
M2 R1
application 2015
(Back-end)
Integrating views November 12,
M3 R1
and designs 2015
(Integrating
front-end and
back-end)
Testing for November 20,
M4 R2
initial release 20015
Issue tracker, December 1,
M5 R2
user reviews, 2015
web design
integration
M6 Final release December 23, R2
2015

Rollno:- 0701CS181059
7. Technical Process
Following would be the languages I would use to develop my
application within the stipulated time period:
Front-end development: Jquery, HTML, CSS, PHP.

Back-end development: PHP, MySQL.
For Android app: Java on Android SDK.
DDS
A design specification is a written document that explains your
product and specifies what you want it to perform as well as how
the user should interact with it. While it may seem laborious to
write everything down, it is the most crucial thing you can do
in the early stages of product design and development. This is
because the design specs direct the whole scope of your product
development.
As a product owner, you should have a clear understanding of

what the product should be like, how it should look like, how
users should interact with it, etc. You are the only person who
can clearly and in detail describe your future product’s desired
characteristics. By drawing up a design specification document
at the initial stage of product development, you can save time
and money, create the perfect product that meets your
expectations, make the process easier for designers, and much
more.

Rollno:- 0701CS181059
The role of specification in the design process has an impact on
its development. The specification is crucial in the product
development process and it has been discovered to play a number
of roles, including:
• Designer guidance.
• Identify the intercommunication between requirements.
• Checklist, e.g., at meetings or workshops.
• An agreement within the design team and as a contract with
the customer, e.g., a supplier agreement, to perform the
design task.
• Trace the probability of propagation of change.
• Product overview.
The key elements of a software specification are:
• Purpose.
• Broad description.
• Detailed requirements.
The greatest software specification documents describe how the
software will interact with other software when it is embedded
in hardware. Real-world users are also taken into account in
good software specification documents.
Result:- Hence we have learned about the Development of SRS and

DDS.

Rollno:- 0701CS181059
Experiment 3
Aim:- To study and classify Unified Modeling Language

(UML) and installation.
Theory:-
UML stands for Unified Modeling Language. It’s a rich language
to model software solutions, application structures, system
behavior and business processes.

Rollno:- 0701CS181059
Unified Modeling Language (UML) is a general purpose modelling
language. The main aim of UML is to define a standard way to
visualize the way a system has been designed. It is quite
similar to blueprints used in other fields of engineering.
UML is not a programming language, it is rather a visual
language. We use UML diagrams to portray the behavior and
structure of a system. UML helps software engineers, businessmen
and system architects with modelling, design and analysis. The
Object Management Group (OMG) adopted Unified Modelling Language
as a standard in 1997. Its been managed by OMG ever since.
International Organization for Standardization (ISO) published
UML as an approved standard in 2005. UML has been revised over
the years and is reviewed periodically.
Do we really need UML?
• Complex applications need collaboration and planning from
multiple teams and hence require a clear and concise way to
communicate amongst them.
• Businessmen do not understand code. So UML becomes
essential to communicate with non programmers essential
requirements, functionalities and processes of the system.
• A lot of time is saved down the line when teams are able to
visualize processes, user interactions and static structure
of the system.
UML is linked with object oriented design and analysis. UML
makes the use of elements and forms associations between them to
form diagrams. Diagrams in UML can be broadly classified as:
1. Structural Diagrams – Capture static aspects or structure
of a system. Structural Diagrams include: Component
Diagrams, Object Diagrams, Class Diagrams and Deployment
Diagrams.
2. Behavior Diagrams – Capture dynamic aspects or behavior of
the system. Behavior diagrams include: Use Case Diagrams,
State Diagrams, Activity Diagrams and Interaction Diagrams.

Rollno:- 0701CS181059
StarUML installation in ubuntu:-

Simple terminal commands for StarUML installation.
Sta
cd ~/Downloads rUM
wget http://staruml.io/download/releases/StarUML-3.0.1-
x86_64.AppImage L
ins
tallation in Windows:-
Goto official website of StarUML “https://staruml.io/download”
and download windows msi installer. Running the downloaded msi
file will install starUML on your machine.
Result:- Hence we have learned about the UML doument and

installation of a software utility “starUML” in ubuntu and
windows machine.

Rollno:- 0701CS181059
Experiment 4
Aim:-Prepare and draw class diagram using UML tools.

Theory:-
Class Diagram
Class diagrams are the main building block of any object-
oriented solution. It shows the classes in a system, attributes,
and operations of each class and the relationship between each
class.
In most modeling tools, a class has three parts. Name at the
top, attributes in the middle and operations or methods at the
bottom. In a large system with many related classes, classes are
grouped together to create class diagrams. Different
relationships between classes are shown by different types of
arrows. Here for example we are making a simple class diagram of
a market model.

Rollno:- 0701CS181059
StarUML is a software unility for the UML document making.
Result:- Hence we have seen use of starUML for making of a

class diagram.

Rollno:- 0701CS181059
Experiment 5
Aim:-Explain use case diagram.
Theory:-
A use case diagram is used to represent the dynamic behavior of
a system. It encapsulates the system's functionality by
incorporating use cases, actors, and their relationships. It
models the tasks, services, and functions required by a
system/subsystem of an application. It depicts the high-level
functionality of a system and also tells how the user handles a
system.
The main purpose of a use case diagram is to portray the dynamic

aspect of a system. It accumulates the system's requirement,
which includes both internal as well as external influences. It
invokes persons, use cases, and several things that invoke the
actors and elements accountable for the implementation of use
case diagrams. It represents how an entity from the external
environment can interact with a part of the system.
Following are the purposes of a use case diagram given below:

1. It gathers the system's needs.
2. It depicts the external view of the system.
3. It recognizes the internal as well as external factors
that influence the system.
4. It represents the interaction between the actors.

Rollno:- 0701CS181059
Example case:-
Here the Web Customer actor makes use of any online shopping
website to purchase online. The top-level uses are as follows;
View Items, Make Purchase, Checkout, Client Register. The View
Items use case is utilized by the customer who searches and view
products. The Client Register use case allows the customer to
register itself with the website for availing gift vouchers,
coupons, or getting a private sale invitation. It is to be noted
that the Checkout is an included use case, which is part of
Making Purchase, and it is not available by itself.
Result:- Hence we have learned about the use case representation

and a example case.

Rollno:- 0701CS181059
Experiment 6
Aim:-Describe entity relationship diagram using UML tool.
Theory:-
Components of ER-Diagram
ER model is having the above mentioned terminology in used which

formation of a ER Model. An entity can have attributes. These
attributes can have various types. Entity have relation with
other relation. There relation can be of listed types.
For Example:-

Rollno:- 0701CS181059
Example 1.
here project is entity which have attributes of Name,

Dob and many more. This entity is related to
other entities using relation representing arrows.
These are the graphical representation tool of ER-diagram scheme
Mapping Constraints
• A mapping constraint is a data constraint that expresses

the number of entities to which another entity can be
related via a relationship set.

Rollno:- 0701CS181059
• It is most useful in describing the relationship sets that
involve more than two entity sets.
• For binary relationship set R on an entity set A and B,
there are four possible mapping cardinalities. These are as
follows:
1. One to one (1:1)
2. One to many (1:M)
3. Many to one (M:1)
4. Many to many (M:M)
Generalization
• Generalization is like a bottom-up approach in which two or

more entities of lower level combine to form a higher level
entity if they have some attributes in common.
• In generalization, an entity of a higher level can also
combine with the entities of the lower level to form a
further higher level entity.
• Generalization is more like subclass and superclass system,
but the only difference is the approach. Generalization
uses the bottom-up approach.
• In generalization, entities are combined to form a more
generalized entity, i.e., subclasses are combined to make a
superclass.
Specialization
• Specialization is a top-down approach, and it is opposite

to Generalization. In specialization, one higher level
entity can be broken down into two lower level entities.
• Specialization is used to identify the subset of an entity
set that shares some distinguishing characteristics.
• Normally, the superclass is defined first, the subclass and
its related attributes are defined next, and relationship
set are then added.
Aggregation
In aggregation, the relation between two entities is treated as
a single entity. In aggregation, relationship with its
corresponding entities is aggregated into a higher level entity.

Rollno:- 0701CS181059
For example: Center entity offers the Course entity act as a
single entity in the relationship which is in a relationship
with another entity visitor. In the real world, if a visitor
visits a coaching center then he will never enquiry about the
Course only or just about the Center instead he will ask the
enquiry about both.
Result:- Hence we learned about the ER Diagram.

Rollno:- 0701CS181059
Experiment 7
Aim:-Given activity diagram defination and description.
Theory:-
The basic purposes of activity diagrams is similar to other four
diagrams. It captures the dynamic behavior of the system. Other
four diagrams are used to show the message flow from one object
to another but activity diagram is used to show message flow
from one activity to another.
Activity is a particular operation of the system. Activity
diagrams are not only used for visualizing the dynamic nature of
a system, but they are also used to construct the executable
system by using forward and reverse engineering techniques. The
only missing thing in the activity diagram is the message part.
It does not show any message flow from one activity to another.
Activity diagram is sometimes considered as the flowchart.
Although the diagrams look like a flowchart, they are not. It
shows different flows such as parallel, branched, concurrent,
and single.
The purpose of an activity diagram can be described as −
• Draw the activity flow of a system.
• Describe the sequence from one activity to another.
• Describe the parallel, branched and concurrent flow of the

system.
Activity diagram can be used for −
• Modeling work flow by using activities.
• Modeling business requirements.
• High level understanding of the system's functionalities.

• Investigating business requirements at a later stage.

Rollno:- 0701CS181059
For example if a customer arrives at the restaurant then the
customer-staff interaction can be defined as.
Customer-Staff activity diagram

Activity diagrams are mainly used as a flowchart that consists
of activities performed by the system. Activity diagrams are not
exactly flowcharts as they have some additional capabilities.
These additional capabilities include branching, parallel flow,
swimlane, etc.
Before drawing an activity diagram, we must have a clear
understanding about the elements used in activity diagram. The
main element of an activity diagram is the activity itself. An
activity is a function performed by the system. After
identifying the activities, we need to understand how they are
associated with constraints and conditions. Before drawing an
activity diagram, we should identify the following elements −
• Activities
• Association
• Conditions
• Constraints

Rollno:- 0701CS181059
Once the above-mentioned parameters are identified, we need to
make a mental layout of the entire flow. This mental layout is
then transformed into an activity diagram.
Result:- Hence we have learned about the activity diagram and

its example.

Rollno:- 0701CS181059

Ujjain Engineering College: Department of Computer Science and Engineering

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ujjain Engineering College: Department of Computer Science and Engineering

Uploaded by

Copyright:

Available Formats

UJJAIN ENGINEERING COLLEGE

Academic Year: 2021-2022

Submitted To:- Assistant Professor Rahul Sharma Submitted By :- VIVEK AJMERI

Department Computer Science and Engineering 1

Aim:- Introduction to software engineering and

Software Managment go in hand to hand with Software

Use of a proper development methodology makes a program

2 SDLC(Software Development Life Cycle

Department Computer Science and Engineering 2

Types of Software Development Models:-

I. The Waterfall Model.

Department Computer Science and Engineering 3

Water Fall Model Graphical Representation

Designing:- The requirement specifications from first phase

Department Computer Science and Engineering 4

Testing:- All the units developed in the implementation phase

Maintenance:- There are some issues which come up in the

All these phases cascaded to each other. In this method the

Department Computer Science and Engineering 5

Department Computer Science and Engineering 6

Department Computer Science and Engineering 7

Department Computer Science and Engineering 8

Department Computer Science and Engineering 9

Result:- Hence we have learned about the Software Development and

Department Computer Science and Engineering 10

Aim:- Development of Software Requirement Specification

Project Plan: MeetUrMate

Department Computer Science and Engineering 11

Department Computer Science and Engineering 12

Department Computer Science and Engineering 13

Department Computer Science and Engineering 14

Front-end development: Jquery, HTML, CSS, PHP.

As a product owner, you should have a clear understanding of

Department Computer Science and Engineering 15

The key elements of a software specification are:

Result:- Hence we have learned about the Development of SRS and

Department Computer Science and Engineering 16

Aim:- To study and classify Unified Modeling Language

Department Computer Science and Engineering 17

Department Computer Science and Engineering 18

StarUML installation in ubuntu:-

Result:- Hence we have learned about the UML doument and

Department Computer Science and Engineering 19

Aim:-Prepare and draw class diagram using UML tools.

Department Computer Science and Engineering 20

StarUML is a software unility for the UML document making.

Result:- Hence we have seen use of starUML for making of a

Department Computer Science and Engineering 21

Aim:-Explain use case diagram.

The main purpose of a use case diagram is to portray the dynamic

Following are the purposes of a use case diagram given below:

Department Computer Science and Engineering 22

Result:- Hence we have learned about the use case representation

Department Computer Science and Engineering 23

Aim:-Describe entity relationship diagram using UML tool.

ER model is having the above mentioned terminology in used which

Department Computer Science and Engineering 24

here project is entity which have attributes of Name,

• A mapping constraint is a data constraint that expresses

Department Computer Science and Engineering 25

• Generalization is like a bottom-up approach in which two or

• Specialization is a top-down approach, and it is opposite

Department Computer Science and Engineering 26