LIST OF EXPERIMENTS

SI.No. Name of the Experiment Date of Date of Faculty

Experiment Submission Signature

1.
Academics (Course Registration
System, Student marks analyzing
system)

2. E-Commerce ( various online

shopping portals like FlipKart
/Amazon/Myntra)
 SOFTWARE ENGINEERING LAB MANUAL

SOFTWARE BENGINEERING THEORY

SOFTWARE DEVELOPMENT LIFE CYCLE

SDLC, or Software Development Life Cycle, is a set of steps used to create software applications.
These steps divide the development process into tasks that can then be assigned, completed, and
measured.
What is the Software Development Life Cycle?
Software Development Life Cycle is the application of standard business practices to building

Build, Document, Test, Deploy, and Maintain. Some project managers will combine, split, or omit

software development projects.

SDLC is a way to measure and improve the development process. It allows a fine-grain analysis of
each step of the process. This, in turn, helps companies maximize efficiency at each stage. As
computing power increases, it places a higher demand on software and developers. Companies
must reduce costs,
achieve these goals by identifying inefficiencies and higher costs and fixing them to run smoothly.
How the Software Development Life Cycle Works?
The Software Development Life Cycle simply outlines each task required to put together a software
application. This helps to reduce waste and increase the efficiency of the development process.
Monitoring also ensures the project stays on track, and continues to be a feasible investment for the
company.
Many companies will subdivide these steps into smaller units. Planning might be broken into
technology research, marketing research, and a cost-benefit analysis. Other steps can merge with
each other. The Testing phase can run concurrently with the Development phase, since developers
need to fix errors that occur during testing.

The Seven Phases of the SDLC

1. Planning
In the Planning phase, project leaders evaluate the terms of the project. This includes calculating

leadership structure.
Planning can also include feedback from stakeholders. Stakeholders are anyone who stands to
benefit from the application. Try to get feedback from potential customers, developers, subject
matter experts, and sales reps.
 SOFTWARE ENGINEERING LAB MANUAL

Planning should clearly define the scope and purpose of the application. It plots the course and
provisions the team to effectively create the software. It also sets boundaries to help keep the
project from expanding or shifting from its original purpose.
2. Define Requirements
Defining requirements is considered part of planning to determine what the application is supposed
to do and its requirements. For example, a social media application would require the ability to
connect with a friend. An inventory program might require a search feature.
Requirements also include defining the resources needed to build the project. For example, a team
might develop software to control a custom manufacturing machine. The machine is a requirement
in the process.
3. Design and Prototyping
The Design phase models the way a software application will work. Some aspects of the design
include:
Architecture Specifies programming language, industry practices, overall design, and use
of any templates or boilerplate
User Interface Defines the ways customers interact with the software, and how the
software responds to input
Platforms Defines the platforms on which the software will run, such as Apple, Android,
Windows version, Linux, or even gaming consoles
Programming Not just the programming language, but including methods of solving
problems and performing tasks in the application
Communications Defines the methods that the application can communicate with other
assets, such as a central server or other instances of the application\
Security Defines the measures taken to secure the application, and may include SSL
traffic encryption, password protection, and secure storage of user credentials
Prototyping can be a part of the Design phase. A prototype is like one of the early versions of
software in the Iterative software development model. It demonstrates a basic idea of how the
- esign can be shown to stakeholders. Use feedback o

make a change in the Development phase.

4. Software development
This is the actual writing of the program. A small project might be written by a single developer,
while a large project might be broken up and worked by several teams. Use an Access Control or
Source Code Management application in this phase. These systems help developers track changes
to the code. They also help ensure compatibility between different team projects and to make sure
target goals are being met.
 SOFTWARE ENGINEERING LAB MANUAL

The coding process includes many other tasks. Many developers need to brush up on skills or work
as a team. Finding and fixing errors and glitches is critical. Tasks often hold up the development
process, such as waiting for test results or compiling code so an application can run. SDLC can
anticipate these delays so that developers can be tasked with other duties.
Software developers appreciate instructions and explanations. Documentation can be a formal
process, including wiring a user guide for the application. It can also be informal, like comments in
the source code that explain why a developer used a certain procedure. Even companies that strive

first launch. It can be video tutorials for complex tasks. Written documentation like user guides,

5. Testing

be automated, like security testing. Other testing can only be done in a specific environment
consider creating a simulated production environment for complex deployments. Testing should
ensure that each function works correctly. Different parts of the application should also be tested to
work seamlessly together performance test, to reduce any hangs or lags in processing. The testing
phase helps reduce the number of bugs and glitches that users encounter. This leads to a higher user
satisfaction and a better usage rate.
6. Deployment
In the deployment phase, the application is made available to users. Many companies prefer to
automate the deployment phase. This can be as simple as a payment portal and download link on
the company website. It could also be downloading an application on a smartphone.
Deployment can also be complex. Upgrading a company-wide database to a newly-developed
application is one example. Because there are several other systems used by the database,
integrating the upgrade can take more time and effort.
7. Operations and Maintenance
At this point, the development cycle is almost finished. The application is done and being used in
the field. The Operation and Maintenance phase is still important, though. In this phase, users

new development cycles.

In addition to bug fixes, models like Iterative development plan additional features in future
releases. For each new release, a new Development Cycle can be launch
Unified Modeling Language (UML) :
Unified Modeling Language (UML) is a standardized (ISO/IEC 19501:2005), general-purpose
modeling language in the field of Software Engineering. The Unified Modeling Language includes
 SOFTWARE ENGINEERING LAB MANUAL

a set of graphic notation techniques to create visual models of object-oriented software-intensive

systems. Unified Modeling Language (UML) combines techniques from data modeling (Entity
Relationship Diagrams), business modeling (work flows), object modeling, and component
modeling. It can be used with all processes, throughout the software development life cycle, and
across different implementation technologies. The UML offers a standard way to visualize a
system's architectural blueprints, including elements such as: activities, actors, business processes,
database schemas, (logical) components, programming language statements, reusable software
components.
1. History
The Unified Modeling Language was developed by Grady Booch, Ivar Jacobson and James
Rumbaugh at Rational Software in the 1990s. It was adopted by the Object Management Group
(OMG) in 1997, and has been managed by this organization ever since. In 2000 the Unified
Modeling Language was accepted by the International Organization for Standardization (ISO) as
industry standard for modeling software-intensive systems. The current version of the UML is 2.4.1
published by the OMG in August 2011.
2. Introduction
The Unified Modeling Language (UML) is a standard language for writing software blueprints. The
UML may be used to visualize, specify, construct, and document the artefacts of a software
intensive system. The UML is appropriate for modelling systems ranging from enterprise
information systems to distributed Web-based applications and even to hard real time embedded
systems.
Even though it is expressive, the UML is not difficult to understand and to use. Learning to apply
the UML effectively starts with forming a conceptual model of the language, which requires
learning three major elements: the UML's basic building blocks, the rules that dictate how these
building blocks may be put together, and some common mechanisms that apply throughout the
language.The UML is only a language and so is just one part of a software development method.
3. Where Can the UML Be Used?
The UML is proposed primarily for software-intensive systems. It has been used effectively for
such areas as
Enterprise information systems
Banking and financial services
Telecommunications
Transportation
Defence/aerospace
Retail
Medical electronics
 SOFTWARE ENGINEERING LAB MANUAL

Distributed Web-based services

The UML is not limited to modelling software. In fact, it is expressive enough to model non-
software systems, such as workflow in the legal system, the structure and behaviour of a patient
healthcare system, and the design of hardware.
4. Building Blocks of the UML
The vocabulary of the UML comprises of three kinds of building blocks
1. Things
2. Relationships
3. Diagrams

1. Things in the UML

There are four kinds of things in the UML
1. Structural things
2. Behavioural things
3. Grouping things
4. Annotational things
These things are the basic object-oriented building blocks of the UML. You use them to write well-
formed models.

2. Relationships in the UML

There are four kinds of relationships in the UML
1. Dependency
2. Association
3. Generalization
4. Realization
These relationships are the basic relational building blocks of the UML. You use them to write
well-formed models.

3. UML Standard Diagrams

In the previous chapters we have discussed about the building blocks and other necessary elements
of UML. Now we need to understand where to use those elements.
The elements are like components which can be associated in different ways to make complete
UML pictures which is known as diagram. So it is very important to understand the different
diagrams to implement the knowledge in real life systems.
Any complex system is best understood by making some kind of diagrams or pictures. These
diagrams have a better impact on our understanding. So if we look around then we will realize that
 SOFTWARE ENGINEERING LAB MANUAL

the diagrams are not a new concept but it is used widely in different form in different industries.
We prepare UML diagrams to understand a system in better and simple way. A single diagram is
not enough to cover all aspects of the system. So UML defines various kinds of diagrams to cover
most of the aspects of a system.
You can also create your own set of diagrams to meet your requirements. There are two broad
categories of diagrams and then are again divided into sub-categories,
3.1. Structural Diagrams
3.2.Behavioural Diagrams

3.1 Structural Diagrams

The structural diagramsrepresent the static aspect of the system. These static aspects represent those
parts of a diagram which forms the main structure and therefore stable. These static parts are
represents by classes, interfaces, objects, components and nodes.
The four structural diagrams are:
Class diagram
Object diagram
Component diagram
Deployment diagram

3.1.1 Class Diagrams

Class diagrams are the most common diagrams used in UML. Class diagram consists of classes,
interfaces, associations and collaboration. Class diagrams basically represent the object oriented
view of a system which is static in nature. Active class is used in a class diagram to represent the
concurrency of the system. Class diagram represents the object orientation of a system. So it is
generally used for development purpose. This is the most widely used diagram at the time of system
construction.

3.1.2 Object Diagram

Object diagrams can be described as an instance of class diagram. So these diagrams are more close
to real life scenarios where we implement a system. Object diagrams are a set of objects and their
relationships just like class diagrams and also represent the static view of the system. The usage of
object diagrams is similar to class diagrams but they are used to build prototype of a system from
practical perspective.

3.1.3 Component Diagram

Component diagrams represent a set of components and their relationships. These components
 SOFTWARE ENGINEERING LAB MANUAL

consist of classes, interfaces or collaborations. So Component diagrams represent the

implementation view of a system. During design phase software artifacts (classes, interfaces etc.) of
a system are arranged in different groups depending upon their relationship. Now these groups are
known as components. Finally, component diagrams are used to visualize the implementation.

3.1.4 Deployment Diagram

Deployment diagrams are a set of nodes and their relationships. These nodes are physical entities
where the components are deployed. This is generally used by the deployment team.
Note: If the above descriptions and usages are observed carefully then it is very clear that all the
diagrams are having some relationship with one another. Component diagrams are dependent upon
the classes, interfaces etc. which are part of class/object diagram. Again the deployment diagram is
dependent upon the components which are used to make a component diagrams.

3.2. Behavioral Diagrams

Any system can have two aspects, static and dynamic. So a model is considered as complete when
both the aspects are covered fully.
Behavioral diagrams basically capture the dynamic aspect of a system. Dynamic aspect can be
further described as the changing/moving parts of a system.
UML has the following five types of behavioral diagrams,
Use case diagram
Sequence diagram
Collaboration diagram
State-chart diagram
Activity diagram

3.2.1 Use case Diagram

Use case diagrams are a set of use cases, actors and their relationships. They represent the use case
view of a system.
A use case represents a particular functionality of a system. So use case diagram is used to describe
the relationships among the functionalities and their internal/external controllers. These controllers
are known as actors.

3.2.2 Sequence Diagram

A sequence diagram is an interaction diagram. From the name it is clear that the diagram deals with
some sequences, which are the sequence of messages flowing from one object to another.
Interaction among the components of a system is very important from implementation and
 SOFTWARE ENGINEERING LAB MANUAL

execution perspective.

3.2.3 Collaboration Diagram

Collaboration diagram is another form of interaction diagram. It represents the structural
organization of a system and the messages sent/received. Structural organization consists of objects
and links.
The purpose of collaboration diagram is similar to sequence diagram. But the specific purpose of
collaboration diagram is to visualize the organization of objects and their interaction.

3.2.4 State-chart Diagram

Any real time system is expected to be reacted by some kind of internal/external events. These
events are responsible for state change of the system.
State-chart diagram is used to represent the event driven state change of a system. It basically
describes the state change of a class, interface etc. State-chart diagram is used to visualize the
reaction of a system by internal/external factors.

3.2.5 Activity Diagram

Activity diagram describes the flow of control in a system. So it consists of activities and links. The
flow can be sequential, concurrent or branched.
Activities are nothing but the functions of a system. Numbers of activity diagrams are prepared to
capture the entire flow in a system. Activity diagrams are used to visualize the flow of controls in a
system. This is prepared to have an idea of how the system will work when executed.

Note: Dynamic nature of a system is very difficult to capture. So UML has provided features to
capture the dynamics of a system from different angles. Sequence diagrams and collaboration
diagrams are isomorphic so they can be converted from one another without losing any information.
This is also true for state-chart and activity diagram.
 SOFTWARE ENGINEERING LAB MANUAL

PROGRAM 1: Academics (Course Registration System, Student marks analyzing system)

1.1 AIM : Course Registration System

1. PROBLEM STATEMENT:
The software which displays the list of courses available for the mark that the student get
and the student can able to allocate best course from the choice available. It displays and allocates
courses based on student ranking. The student ranking is based on marks, caste and community.
Based on caste and community the ranking may varied. This software allows the student to choose
the best college for the available courses.

2. OVERALL DESCRIPTIONS:
2.1 MODULES:
1.Login
2.student_info
3.course_details
4.course_registration
5.confirmation
2.2 MODULE DELIVARABLES:
Login:
Basicflow:To authenticate the user,the student has to enter username and password
Alternateflow:If the password is wrong,it will ask the student to answer security question and
retrieve the password
Precondition:The system asks the student to enter the password
Postcondition:On success,the student displays the student information
Student_info:
Basicflow:The system displays the basic information about the student.It should be verified by the
user.
Alternateflow:If there is any error in displayed information ,the student can do changes.
Precondition:The student checks the basic details displayed.
Postcondition:After verifying all the details,it should be updated and moves on to the next state.
Course_details:
Basicflow:The courses that are available for the student are displayed and the student should select
one.
Alternateflow:If the student finds that the courses available for him are not displayed,he can report
it.
Precondition:The details of the corses available for his mark should be known by the user.
 SOFTWARE ENGINEERING LAB MANUAL

Postcondition:After selecting the course,it will moves on to the next stage.

Course_registration:
Basicflow:All the colleges that are available for the courses are displayed.
Alternateflow:If the student finds that the colleges are displayed in error,he can report it.
Precondition:The student should have to select the colleges available.
Postcondition:After registering the course,it will move on to the next stage.
Confirmation:
Basicflow:The college and the course that the student choose is displayed.
Alternateflow:If the student finds any fault regarding his course/college,he can report it.
Precondition:The student should have to confirm the college and the course.
Postcondition:The course and the college is confirmed and the student confirms it by choosing
confirm button.

3. UML DIAGRAMS:

3.1. UseCase Diagram:

 SOFTWARE ENGINEERING LAB MANUAL

3.2. Class Diagram:

3.3. ActivityDiagram:
 SOFTWARE ENGINEERING LAB MANUAL

3.4. Component Diagram:

3.5. Deployment Diagram:

3.6. Sequence Diagram:

 SOFTWARE ENGINEERING LAB MANUAL

3.7. Collaboration Diagram:

4. DATABASE DESIGN

Database name: student

Table name : studentdetails

Fields Data type

NAME text
Dob text
MARK integer
Caste text
ADDRESS text
Email text
Gender text

Table name : coursedetails

Fields Data type

Courseavailable text
Timeperiod text
basicmark integer

Table name : conformation

Fields Data type
Availablecolleges text
Paymentmethod text
 SOFTWARE ENGINEERING LAB MANUAL

5. IMPLEMENTATION:
Form1(student login)

Coding:
Private Sub Command1_Click()
If Text1.Text = "student" and Text2.Text = "password" Then
form2.Show
else
msgBox ("incorrect username or password")
End If
End Sub
Private Sub Command2_Click()
End
End Sub

Form2(Student details)
 SOFTWARE ENGINEERING LAB MANUAL

Coding:
Private Sub Command1_Click()
form2.Show
Data1.Recordset.AddNew
Data1.Recordset.Fields("NAME") = Text5.Text
Data1.Recordset.Fields("dob") = Text4.Text
Data1.Recordset.Fields("MARK") = Text3.Text
Data1.Recordset.Fields("caste") = Combo1.Text
Data1.Recordset.Fields("ADDRESS") = Text2.Text
Data1.Recordset.Fields("email") = Text1.Text
Data1.Recordset.Fields("gender") = Combo2.Text
MsgBox ("DETAILS ARE VERIFIED")
Form3.Show
Data1.Recordset.Update
End Sub
Private Sub Command2_Click()
Form1.Show
End Sub
Private Sub Form_Load()
Combo1.AddItem ("BC")
Combo1.AddItem ("SC")
Combo2.AddItem ("male")
Combo2.AddItem ("female")
Combo2.AddItem ("other")
End Sub

Form3(Course details)

Coding:
Private Sub Command1_Click()
Form3.Show
Data1.Recordset.AddNew
Data1.Recordset.Fields("courseavailable") = Combo1.Text
If Option1.Value = True Then
Data1.Recordset.Fields("timeperiod") = "9am-12pm"
Else
 SOFTWARE ENGINEERING LAB MANUAL

Data1.Recordset.Fields("timeperiod") = "1am-4pm"
End If
Data1.Recordset.Fields("basicmark") = Val(Text1.Text)
MsgBox ("course is selected")
Form4.Show
Data1.Recordset.Update
End Sub

Private Sub Command2_Click()

Form2.Show
End Sub
Private Sub Form_Load()
Combo1.AddItem ("BE(ECE)")
Combo1.AddItem ("BE(IT)")
Combo1.AddItem ("BE(CIVIL)")
Combo1.AddItem ("BE(E&I)")
End Sub
Form4(Conformation)

Coding:
Private Sub Command1_Click()
Form4.Show
Data1.Recordset.AddNew
Data1.Recordset.Fields("availablecolleges") = Combo1.Text
Data1.Recordset.Fields("paymentmethod") = Combo2.Text
MsgBox (" your confirmation is registered")
Form1.Show
End Sub
Private Sub Command2_Click()
Form3.Show
End Sub
Private Sub Form_Load()
Combo1.AddItem ("jerusalem college of engineering")
Combo1.AddItem ("prathushya engineering college")
 SOFTWARE ENGINEERING LAB MANUAL

Combo1.AddItem ("tagore engineering college")

Combo2.AddItem ("single payment")
Combo2.AddItem ("2 month once")
Combo2.AddItem ("3 month once")
End Sub

6. TESTING:
Test case ID: Test_01
Test priority
(Low/Medium/High):Medium
Module name: login
Test title :verify login with valid username and password
Precondition: user has invalid username and password
S.NO TEST EXPECTED ACTUAL STATUS NOTES
STEPS RESULTS RESULTS
1 Provide User should The user is able to Success -
valid Be able to move to next
User name login Entry
2 Provide User should be The user is able Success In case of
valid Able to To login wrong
password Login Successfully Password was
given an error
Message box
was
displayed
3 Click login User should be User name and Success Incase user
able to navigate password is gives wrong
to next page validated and next entry the sign
after validation page is displayed in page
remains active
4 Click User should be User navigates to success -
signup able to navigate the signup page
to next page where his user
where user name and
enters his password is
credentials validated

RESULT: The Course registration system was designed and implemented successfully.
 SOFTWARE ENGINEERING LAB MANUAL

1.2 AIM :Student marks analyzing system

1. PROBLEM STATEMENT:
Student marks analyzing system has to be developed for analyzing obtained by the students
who scored in Semester Examination The System should provide following functionalities

Department, Semester, Marks obtained in each subject.

2. The total for each student should be calculated and ranked based on total and pass in all the
subject appeared.
3. The Final report should display rank, percentage, Class, Pass/Fail Status for each student.
2. OVERALL DESCRIPTIONS:
2.1 MODULES:
1.Login
2.student_mark
3. View report
2.2MODULE DELIVARABLES:
1. Login
Basic Flow: This use case starts when the Faculty wishes to Login to the Student Marks Analyzing
System.
1. The System requests that the Faculty enter his/her name and password
2. The Faculty enters his/her name and password
3. The System validates the entered name and password and logs the Faculty into the System
Alternative Flows: Invalid Name/Password
If, in the Basic flow, the Faculty enters an invalid name and/or password, the system displays an
error message. The Faculty chooses to either return to the beginning of the Basic flow or cancel the
login, at which point the use case ends.
Pre-Conditions: None
Post-Conditions: If the use case was successful, the Faculty is now logged into the system. If not,
the system State is unchanged.
2. Student_Mark
Basic flow: The Faculty uses this usecase to enter marks for each student. The faculty enters the
following details namely Roll No, Student Name, Department, Marks for each student.
Alternative Flows: If faculty not entered any details or invalid marks then gives error Message
Pre-Conditions: The Faculty must logged into the system
Post-Conditions: If this Use case was successful, Student Mark Analysis Report will be generated
for the Student.
 SOFTWARE ENGINEERING LAB MANUAL

3. View Report
Basic flow: The Actor uses this usecase view the Report .The report contains the following details
Namely Roll No, Student Name, Marks in each subject, total, class, Pass/Fail Status, No of subjects
failed, Rank.
Apart from this there is a separate report Overall Pass percentage of class, No of students cleared in
First class, Overall Top 3 persons of the class.
Alternative Flow: If the Marks is not entered for all the students the use case will ask the faculty to
the enter the marks.
Pre-Conditions: The Faculty must entered marks for all the students in a class.
Post-Conditions: None
3. UML DIAGRAMS:
3.1. UseCase Diagram:
 SOFTWARE ENGINEERING LAB MANUAL

3.2 Activity Diagram

3.3 Class Diagram

3.4 Sequential Diagram

 SOFTWARE ENGINEERING LAB MANUAL

3.5 Collaboration diagram

3.6 Component Diagram of student info System

3.7 Deployment Diagram of Student info System

 SOFTWARE ENGINEERING LAB MANUAL

4. DATABASE DESIGN
Database name: student
Table name:marks
Fields Data type
student name Text
register number Integer
Pqt Integer
Daa Integer
Mup Integer
Se Integer
Os Integer
Total Integer
Percentage Double
Result Text

5. IMPLEMENTATION:
FORM1 (Login form)

Coding:
Private Sub Command1_Click()

form2.Show
Else

end if
End Sub

Private Sub Command2_Click()

End
End Sub
 SOFTWARE ENGINEERING LAB MANUAL

FORM2 Entry form

Coding:
Private Sub Command1_Click()
Dim total, per, result
Data1.Recordset.AddNew
Data1.Recordset.Fields("sname") = Text1.Text
Data1.Recordset.Fields("regno") = Text2.Text
Data1.Recordset.Fields("m1") = Text3.Text
Data1.Recordset.Fields("m2") = Text4.Text
Data1.Recordset.Fields("m3") = Text5.Text
Data1.Recordset.Fields("m4") = Text6.Text
Data1.Recordset.Fields("m5") = Text7.Text
total = Text3.Text + Text4.Text + Text5.Text + Text6.Text + Text7.Text
Data1.Recordset.Fields("total") = total
per = (total / 5) * 100
Data1.Recordset.Fields("per") = per
If (Text3.Text > 49 And Text4.Text > 49 And Text5.Text > 49 And Text6.Text > 49 And
Text7.Text > 49) Then result = "pass"
Data1.Recordset.Fields("result") = result
Data1.Recordset.Update
MsgBox ("record saved")

Form3.Show

End Sub

Private Sub Command2_Click()

End
End Sub
 SOFTWARE ENGINEERING LAB MANUAL

FORM3 (Display Students)

Coding:
Private Sub Command1_Click()
End
End Sub
 SOFTWARE ENGINEERING LAB MANUAL

6. TESTING:

Test case ID: Test_01

Test priority
(Low/Medium/High):Medium
Module name: login
Test title :verify login with valid username and password
Precondition: user has invalid username and password
S.NO TEST EXPECTED ACTUAL STATUS NOTES
STEPS RESULTS RESULTS
1 Provide User should The user is able to Success -
valid Be able to move to next
User name login Entry
2 Provide User should be The user is able Success Incase of
valid Able to To login wrong
password Login Successfully Password was
given an error
Message box
was
Displayed
3 Click login User should be User name and Success Incase user
able to navigate to password is gives wrong
next page after validated and next entry the sign
validation page is displayed in page
remains active
4 Click signup User should be User navigates to success -
able to navigate to the signup page
next page where where his user
user enters his name and
credentials password is
validated

RESULT:The Student marks analyzing system was designed and implemented successfully.
 SOFTWARE ENGINEERING LAB MANUAL

PROGRAM 4 : E-Commerce ( various online shopping portals like FlipKart / Amazon

/Myntra)

AIM : E-Commerce ( various online shopping portals likeFlipKart/Amazon/Myntra)

3. DESIGN
3.1 USECASE DIAGRAM
 SOFTWARE ENGINEERING LAB MANUAL

CLASS DIAGRAM

ACTIVITY DIAGRAM
 SOFTWARE ENGINEERING LAB MANUAL

SEQUENCE DIAGRAM

COLLABORATION DIAGRAM:
 SOFTWARE ENGINEERING LAB MANUAL

Online shopping component diagram

Online shopping web application UML deployment diagram

RESULT:The E-COMMERCE system was designed and implemented successfully.

SOFTWARE ENGINEERING LAB MANUAL