Project - Software Engineering Techniques

EX.
NO : 1
INTRODUCTION TO SOFTWARE ENGINEERING TECHNIQUES
AIM:
To study the basics of Software Engineering Techniques
PROJECT PLANNING:
The objective of software project planning is to provide a framework that enables the manager to make
reasonable estimates of resources cost and schedule. The first activity in software project planning is the
determination of software scope. Software scope describes the data and Control to be processed, function,
performance, constraints, interfaces and reliability. The second software-planning task is estimation of the
resources required to accomplish the software development effort. Software cost and effort estimation is an
important factor to be considered. Variables like human, technical, environmental, and political will affect the
ultimate cost of software and effort applied to develop it.
SOFTWARE REQUIREMENTS ANALYSIS:

Requirements Analysis is a software engineering task that bridges the gap between system level
requirement engineering and software. Requirements engineering activities result in the specification of
softwares operational characteristics such as data and functional behavior. Requirements analysis allows the
software Engineer to refine the software allocation and build models of the data, functional and behavioral
domain that will be treated by software.
DATA MODELING:
The data model consist of three interrelated pieces of information the data objects, the attributes that
describes the data object and the relationships that connect data objects to one another. A data object is the
representation of almost any composite information that must be understood by software. Composite
information means something that has number of different properties or attributes. A data object can be an
external entity, a thing, an occurrence or event, a role, an organizational unit, a place or a structure. The
attributes define the properties of data objects and take on one of three different characteristics. They can be
used to name an instance of the data object, describes the instance or make reference to another instance in
another table. Data objects are connected to one another in different ways. Data model must be capable of
representing the number of occurrences of object in a given relationship.
1
SOFTWARE TESTING:
Software testing is the critical element of software quality assurance and represents the ultimate review
of specification design and code generation. Testing is a process of executing a program with the intent of
finding an error. The objective is to design test the systematically uncover different classes of errors and to do
so with minimum amount of time and effort. Different types of testing approaches used are black box testing
and white box testing. Black box test are used to demonstrate that the s/w functions are operational that is input
is properly accepted and output is correctly produced. White box testing of software is predicated on a close
examination of procedural detail. Logical paths through the software are tested by providing test cases that
exercise specifies sets of condition and loops. The status of the program may be examined at various points to
determine if the expected status corresponds to the actual status.
SOFTWARE DEBUGGING:
It is an exercise to connect manifestation of the error and the internal cause of the error. Debugging
techniques include:
Break points - Break point is a computer program at which execution can be suspended to permit
manual or automated monitoring of program performance or results.
Desk checking - Desk checking is a technique in which code listings, test results or other documentation
are visually examined, usually by the person that generated them, to identify errors, violations of
development standards or other problems.
Dumps - Dumps display some aspect of a computer programs execution state, usually the contents of
internal storage or registers.
Single-step operation- In this debugging technique a single computer instruction is executed in
response to an external signal.
Traces - A record of the execution of computer program, showing the sequence of instructions executed
the names and values of variables or both.
RESULT:
Thus the basics of Software Engineering Techniques are studied.
2
EX. NO: 2
PROBLEM ANALYSES AND PROJECT PLANNING
AIM:
The basic aim of planning is to look into future, identify the activities that need to be done complete the
project successfully and plan the scheduling and resource allocation for these activities.
DESCRIPTION:
Planning is the most important management activity. The input to the planning activity is the
requirements specification, the output of this space is the project plan, which is a document describing the
different aspects of the plan. The project plan is the instrument in driving development process to remaining
phases.
ISSUES OF PROJECT PLAN:

The major issues the project plan addresses are:
1. Cost Estimation
2. Schedule and milestones
3. Personnel Plan
4. Software Quality Assurance Plans
5. Configuration Management Plans
6. Project Monitoring Plans
7. Risk Management
DOCUMENTS:
1. Cost Estimation
2. Schedule
3. Personnel Plan
RESULT:
Thus the project-planning phase of software development is studied.
3
EX.NO.3
SOFTWARE REQUIREMENTS ANALYSIS
AIM:
The basic aim of software requirement analysis is to properly understand the basic needs of Software
required developing a system. Problem analysis and requirement specification activities overlap with movement
both activities to other.
REQUIREMENTS ANALYSIS
Requirements Analysis is the process of understanding the customer needs and expectations from a
proposed system or application and is a well-defined stage in the Software Development Life Cycle model.
Requirements are a description of how a system should behave or a description of system Properties or
attributes. It can alternatively be a statement of what an application is expected to do. Given the multiple
levels of interaction between users, business processes and devices in global corporations today, there are
simultaneous and complex requirements from a single application, from various levels within an organization
and outside it as well.
The Software Requirements Analysis Process covers the complex task of eliciting and documenting the
requirements of all these users, modeling and analyzing these requirements and documenting them as a basis for
system design. A dedicated and specialized Requirements Analyst is best equipped to handle the job. The
Requirements Analysis function may also fall under the scope of Project Manager, Program Manager or
Business Analyst, depending on the organizational hierarchy.
Software Requirements Analysis and Documentation Processes are critical to software Project success.
Requirements engineering is an emerging field, which deals with the systematic handling of requirements.
STEPS IN THE REQUIREMENTS ANALYSIS PROCESS

I. Fix system boundaries
This initial step helps in identifying how the new application integrates with the business processes, how
it fits into the larger picture and what its scope and limitations will be.
II. Identify the customer

In more recent times there has been a focus on identifying who the users or customers of an
application are. Referred to broadly as the stake holders, these indicate the group or groups of people who will
4
be directly or indirectly impacted by the new application. By defining in concrete terms that the intended user
is, the Requirements Analyst knows in advance where he has to look for answers. The Requirements Elicitation
Process should focus on the wish list of this defined group to arrive at a valid requirements list.
III. Requirements elicitation

Information is gathered from the multiple stakeholders identified. The Requirements Analyst draws out
from each of these groups what their requirements from the application are and what they expect the application
to accomplish. Considering the multiple stakeholders involved, the list of requirements gathered in this manner
could run into pages. The level of detail of the requirements list is based on the number and size of user groups,
the degree of complexity of business processes and the size of the application.
a) Problems faced in Requirements Elicitation
Ambiguous understanding of processes
Inconsistency within a single process by multiple users
Insufficient input from stakeholders
Conflicting stakeholder interests
Changes in requirements after project has begun
A Requirements Analyst has to interact closely with multiple work-groups, often with Conflicting goals, to
arrive at a bona fide requirements list. Strong communication and people skills along with sound programming
knowledge are prerequisites for an expert Requirements Analyst.
b) Tools used in Requirements Elicitation
Traditional methods of Requirements Elicitation included stakeholder interviews and focus group studies.
Other methods like flowcharting of business processes and the use of existing documentation like user manuals,
organizational charts, process models and systems or process specifications, on-site analysis, interviews with
end-users, market research and competitor analysis were also used extensively in Requirements Elicitation.
However current research in Software Requirements Analysis Process has thrown up modern tools that are
better equipped to handle the complex and multilayered process of Requirements Elicitation. Some of the
current Requirements Elicitation tools in use are:
Prototypes
Use cases
Data flow diagrams
Transition process diagrams
User interfaces
5
IV. Requirements Analysis Process
Once all stakeholder requirements have been gathered, a structured analysis of these can be done after
modeling the requirements. Some of the Software Requirements Analysis techniques used are requirements
animation, automated reasoning, knowledge-based critiquing, consistency checking, and analogical and case-
based reasoning.
V. Requirements Specification
Requirements, once elicited, modeled and analyzed should be documented in clear, unambiguous terms.
A written requirements document is critical so that its circulation is possible among all stakeholders including
the client, user-groups, the development and testing teams. Current requirements engineering practices reveal
that a well-designed, clearly documented Requirements Specification is vital and serves as
Base for validating the stated requirements and resolving stakeholder conflicts, if any
Contract between the client and development team
Basis for systems design for the development team
Benchmark for project managers for planning project development lifecycle and goals
Source for formulating test plans for QA and testing teams
Resource for requirements management and requirements tracing
Basis for evolving requirements over the project life span
Software requirements specification involves scoping the requirements so that it meets the customers vision. It
is the result of collaboration between the end-user who is often not a technical expert, and a Technical/Systems
Analyst, who is likely to approach the situation in technical terms.
The software requirements specification is a document that lists out stakeholders needs and communicates
these to the technical community that will design and build the system. The challenge of a well-written
requirements specification is to clearly communicate to both these groups and all the sub-groups within. To
overcome this, Requirements Specifications may be documented separately as
User Requirements - written in clear, precise language with plain text and use cases, for the benefit of
the customer and end-user
System Requirements - expressed as a programming or mathematical model, addressing the
Application Development Team and QA and Testing Team. Requirements Specification serves as a
starting point for software, hardware and database design. It describes the function (Functional and Non-
Functional specifications) of the system, performance of the system and the operational and user-
interface constraints that will govern system development.
6
VI. Requirements Management
Requirements Management is the comprehensive process that includes all aspects of software
requirements analysis and additionally ensures verification, validation and trace ability of requirements.
Effective requirements management practices guarantee that all system requirements are stated unambiguously,
that omissions and errors are corrected and that evolving specifications can be incorporated later in the project
lifecycle.
RESULT:
Thus the requirement analyses of software development are studied.
7
EX.NO.4
DATA MODELING
AIM:
To study the concepts of data modeling.
DATA MODEL:
A Data model is an abstract representation of a system constructed to understand the system before building or
modifying it. It is a simple presentation of reality. It provides the blue prints of the system. The models are built
to provide better understanding of the system that is being developed. The models of complex systems are built
to comprehend the entire system. Data modeling is necessary for communication among project teams.
ADVANTAGES OF DATA MODELING:

1. Help in visualizing a system as it is or as it is expected.
2. Permit us to specify the structure or behavior of a system and it allows mastering the complex system.
3. Provide us a template that guides us in constructing a system and used to generate usable work products.
4. Document the decisions that are made.
5. Help us to capture and precisely state requirements and domain knowledge so that all stake holders may
understand and agree on them.
6. Give us an idea to carry out certain activities such as organize, find, filter, retrieve, examine and edit
information about large systems.
7. Provide guidelines to explore multiple solutions economically.
8. Enable us to capture design decisions in a mutable form separate from the requirements.
9. Enhance and reinforce learning and training and make manipulation of model easy.
10. The total cost involved in the modeling analysis is much lower than the cost of similar experimentation
conducted with a real system.
PRINCIPLES OF MODELING:
Choose the right models
1. Every model may be expressed at different levels of precision.
2. The best models are connected to reality.
3. No single model is sufficient.
8
A Modeling Language must include:
Model elements fundamental modeling concepts and semantics.
Notation Visual rendering of model elements.
Guidelines expression of usage within the trade.
Data Modeling provides
Clarity
Familiarity
Maintenance
Simplification
VISUAL MODELING:
Visual modeling is defined as mapping the real world process of a computer system with a graphical
representation or blue print. It captures essential parts of the system. It is a communication tool, which is used to
analyze the design of our application.
ADVANTAGES:
Captures business process
Enhance communication
Manage complexity
Define architecture
Permits reuse
STATIC AND DYNAMIC DATA MODELING:

STATIC MODEL: It can be viewed as an image of system parameters at rest or specific point in time.
Static models are required to represent the structural or static aspect of a system. Static models presume
stability and an absence of change in data over time. E.g. Class Diagram
DYNAMIC MODEL: It can be viewed as a collection of procedures or behaviors that taken together
reflect the behavior of a system over a period of time. Dynamic relationships show how the business
objects interact for performing tasks. Examples are Interaction diagrams and Activity diagrams.
RESULT:
Thus the data modeling concepts are studied.
9
EX.NO.5
UNIFIED MODELING LANGUAGES
AIM:
To get a detailed description study of Unified Modeling language.
DEFINITION:
The Unified Modeling Language (UML) is a graphical language for visualizing, specifying,
constructing and documenting the artifacts of a software intensive system. UML provides a vocabulary and
the rules for communication and focus on conceptual and physical representation of the system. So it is a
Modeling Language. The UML gives a standard way to write a systems blueprints, covering conceptual things,
such as classes written in a specific programming language, database schemas and reusable software
components.
UML includes both graphical and textual representation. It makes easy to visualize the system and for
better understanding. UML addresses the specification of all the important analysis, design and implementation
decisions and developing and deploying a software- intensive system.
UML models can be directly connected to a variety of programming languages. And it is Sufficiently
expressive and free from any ambiguity to permit the direct execution of models, the simulation of systems and
the instrumentation of running systems. UML produces variety of documents in addition to raw executable
code; the artifacts include Requirements, Architecture, Design, Source code, Project Plans, Test, Prototypes,
and Releases. The UML may be used with any process. Although, it is generally assumed that the process is
architecture centric, use case driven, iterative and incremental.
The UML combines the best of the best from Data modeling concepts (E-R Diagrams), Business
Modeling (workflow), Object Modeling and Component Modeling
UML USAGE:
UML has been effectively used in domains such as: EIS(Enterprise Information System), Banking and
financial services, Telecommunications, Transportation, Defense/Aerospace, Retail, Medical, Electronics,
Scientific and Distributed Web-based services. It can be used with all processes, throughout the development
life cycle and across different implementation Technologies.
10
UML ARCHITECTURE:
Architecture is used to manage different viewpoints and hence control the iterative and incremental
development of systems throughout its lifecycle. Each of the above 5 views can standalone so that the different
stakeholder can focus on the issues of the systems architecture that most concerns them. The five views interact
with one another.
MODELING A SYSTEMS ARCHITECTURE

Vocabulary
Functionality
System Assembly
configuration
management
Performance, System Topology, distribution,
Scalability, throughput Delivery and Installation
UML PRIMARY GOALS:

The Primary goals in the design of UML are:
Provide users a ready-to-use, expressive visual modeling language so that they can develop and
exchange meaningful models.
Provide extensibility and specialization mechanisms to extend the core concepts.
Provide the required formal basics for understanding the modeling Language.
Encourage the growth of the OO tools market.
Support development concepts at higher level.
Integrate best practices and methodologies.
Be independent of particular programming languages and development processes.
UML CONCEPTS:
The UML may be used to visually model
The interaction of the application with the outside world
The behavior of the system
The architecture of the enterprise
The components in the system.
Design View Implementation
11
The UML can be used to support the entire lifecycle
See the interaction with the outside world in use-case diagrams.
Visualize object interaction in sequence and collaboration diagrams.
Look at the structure of the system by examining class diagrams.
View the system architecture by looking the defined packages.
Explore the physical nature of the system using component diagrams.
UML FOUNDATIONS:
The vocabulary of the UML encompasses three kinds of building blocks:
Things Structural, Behavioral, Grouping, Annatational.
Relationships Dependency, Association, Generalization and Realization.
Diagrams Every complex system is best approached through a small set of nearly independent
views of a model. The UML diagrams are classified into static and dynamic diagrams
Static/ Structural Diagrams
1. Class Diagram
2. Object Diagram
3. Interaction Diagram
3.1 Component Diagram
3.2 Deployment Diagram
Dynamic / Behavior Diagrams
1. Use Case Diagram
2. Interaction Diagram
2.1 Sequence Diagram
2.2 Collaboration Diagram
3. State Chart Diagram
4. Activity Diagram
Use-case Diagram: A Use-case diagram is created to visualize the interaction of the system with the outside
world.
Activity Diagram: An activity diagram shows the flow of events within the system.
Sequence diagram: A sequence diagram shows step by step what must happen to accomplish
a piece of functionality provided by the system. A sequence diagram is also known as interaction diagram.
Collaboration Diagram: This type of diagram shows the object and their links to one another. A collaboration
diagram is also known as interaction diagram.
12
Class Diagram: Class diagrams are created to show the structure of the system. Class diagrams contain classes,
relationships and multiplicity indicators. A class is a collection of objects with common - structures, behaviors,
relationships and semantics. The UML notation for class is a compartmented rectangle. The first compartment
shows the name of the class. Each class also has data associated with it, which are represented by set of
activities.
State Chart Diagram: A state chart diagram shows the lifecycle of the single class.
Component Diagram: A Component diagram illustrates the organization and dependencies among software
components.
Deployment diagram: A deployment diagram visualizes the distribution of components across the enterprise.
EXTENDING THE UML:
Stereotypes can be used to extend the UML notational elements. Stereotypes may be used to classify and
extend associations, inheritance, relationships, classes, and components.
Examples:
Class Stereotypes: interface, exception, server page
Association Stereotypes: identifying, non identifying
Dependency Stereotypes: include, extend
Component Stereotypes: subsystem
RULES OF THE UML:
The UML has the following semantic rules to become a well-formed model.
Names - What you can call things, relationships and diagrams.
Scope - The context that gives specific meaning to a name.
Visibility - How those names can be seen and used by others.
Integrity - How things properly and consistently related.
Execution - What it means to run or simulate a dynamic model?
COMMON MECHANISMS IN UML:
The UML is made simpler by the presence of four common mechanisms that apply throughout the language
Specifications
Adornments
Common divisions
Extensibility mechanism
RESULT:
Thus a detailed description of Unified Modeling language is studied.
13
EX.NO.6
ONLINE COURSE REGISTRATION SYSTEM
AIM:
To implement the online course registration project using StarUml and Visual Basic.
PROBLEM ANALYSIS AND PROBLEM PLANNING:

This software is designed in such a way that it gathers information from the candidate if he/she is want
to register a course and display the course details. The system allows the candidate to register the course what
he/she desired.
OBJECTIVES:
The main purpose of creating the document about the software is to know about the list of the
requirement in the software project part of the project to be developed.
It specifies the requirement to develop a processing software part that completes the set of requirement.
SCOPE:
In this specification, we define about the system requirements that are about from the functionality of
the system. It tells the users about the reliability defined in use case specification.
INFRASTRUCTURE:
HARDWARE REQUIREMENTS:
RAM : 256 MB
Processor : Intel Pentium IV
Hard disk : 40 GB
SOFTWARE REQUIREMENTS
Microsoft Visual Basic 6.0
StarUML
Microsoft Access
14
PROBLEM STATEMENT:
Online course registration system has to be developed for registering the course. Students may request a
course catalogue containing list of course offered. This will be helpful for students to make decisions
efficiently. Once the registration process is completed for the student, the registration system sends information
to the billing system so that the student can be billed for the course and verifies the certificate to join the course.
The system is built to be used by students and managed by an administrator.
The student and employee have to login to the system before any processing can be done.
The student can see the courses available to him and register to the course he/she wants.
The administrator can maintain the course details and view all the students who have registered to
any course
SOFTWARE REQUIREMENT ANALYSIS:

The modules of online course registration system is an integrated system that as four modules as part of
it. The modules are as follows
LOGIN FORM:
The student and administrator should login before any process done. The student can login by
his/her unique ID and Password.
STUDENT DETAILS:
The students must provide all his details to register the course. The details about students are
stored in the database.
COURSE REGISTRATION:
The course details are filled by the candidate and finalized.
REGISTRATION CONFIRMATION:
The course registered successfully.
DATA MODELING:
Data modeling provides detail about the system design or blue print of the online course registration
system. It is represented by UML diagrams. Data modeling consists of
Use Case Diagram
Class Diagram
Activity Diagram
Sequence Diagram
Collaboration Diagram
15
State Diagram
Deployment Diagram
Component Diagram
Package Diagram
USE CASE DIAGRAM:

A use case is a methodology used in system analysis to identify, clarify, and organize system
requirements.
The use case is made up of a set of possible sequences of interactions between systems and users in a
particular environment and related to a particular goal.
It is represented using ellipse.
Actor is any external entity that makes use of the system being modeled. It is represented using stick
figure.
The system includes
Student A student should login, enquiry about course details, select and register the course and
pay the fees.
Administrator maintain the database and update the datas to the database.
16
CLASS DIAGRAM:
A class diagram in the unified modeling language (UML) is a type of static structure diagram.
It describes the structure of a system by showing the system's classes, their attributes, and the
relationships between the classes. It is represented using a rectangle with three compartments.
Top compartment have the class name, middle compartment the attributes and the bottom compartment
with operations.
Here 4 classes are defined such as
Student
Administrator
College
Course
17
ACTIVITY DIAGRAM:
STATE DIAGRAM:
18
DEPLOYMENT DIAGRAM:
SEQUENCE DIAGRAM:
19
COLLABORATION DIAGRAM:
COMPONENT DIAGRAM
20
PACKAGE DIAGRAM:
USER INTERFACE LAYER
LOGIN
DOMAIN LAYER
STUDENT DETAILS REGISTRATION

DETAILS
TECHNICAL LAYER
DATA BASE
SYSTEM DESIGN AND IMPLEMENTATION:
FORM1
LOGIN:
Private Sub Submit_Click()
Text1.SetFocus
If Text1.Text = "sabi" And Text2.Text = "sabi123" Then
MsgBox "login successfully"
Form2.Show
Unload Me
21
Else
MsgBox "invalid password"
End If
End Sub
RESET:
Private Sub reset_Click()
Text1.Text = ""
Text2.Text = ""
End Sub
CANCEL:
Private Sub cancel_Click()
Unload Me
End Sub
FORM2:
ADD:
Private Sub insert_Click()
DataEnvironment1.insert Text1.Text, Text2.Text, Text3.Text, Text4.Text, Text5.Text, Text6.Text
22
MsgBox "successfully register"
Form3.Show
End Sub
SEARCH:
Private Sub find_Click()
DataEnvironment1.find Text1.Text
With DataEnvironment1.rsfind
If DataEnvironment1.rsfind.EOF Then
MsgBox "not found"
Else
MsgBox "found"
Text1.Text = DataEnvironment1.rsfind.Fields("candidatename")
Text2.Text = DataEnvironment1.rsfind.Fields("dob")
Text3.Text = DataEnvironment1.rsfind.Fields("resident")
Text4.Text = DataEnvironment1.rsfind.Fields("age")
Text5.Text = DataEnvironment1.rsfind.Fields("mailid")
Text6.Text = DataEnvironment1.rsfind.Fields("qualification")
End If
.Close
End With
23
End Sub
CANCEL:
Private Sub cancel_Click()
Unload Me
End Sub
FORM 3:
UPDATE:
Private Sub update_Click()

DataEnvironment1.update Text1.Text, Text2.Text, Text3.Text
MsgBox "edited"
End Sub
24
FORM 4:
RESULT:
Thus the project Online Course Registration System was developed using STARUML software is done
and code generated successfully.
25
EX.NO.7
STUDENT MARK ANALYZING SYSTEM
AIM:
To implement the Student Mark Analyzing System project using StarUml and Visual Basic.

This software is designed in such a way that it generates the student mark report for school / college.
The system allows the staff to enter the marks details about student and stores the data in database for future
reference.
It simply holds the various mark details of students and it creates the required report, whenever needed.
.The software is a solution to many recurring problems such as managing student mark list and generating
reports. The future enhancements of the project can also be made based on the user requirements.
OBJECTIVES:
The main objective of our project is to develop a student mark analysis system for colleges/school.
This helps the institution to maintain student mark analysis report for each and every student separately
and secure way.
It specifies the requirement to develop a processing software part that completes the set of requirement.
SCOPE:
In this specification, we define about the system requirements that are about from the functionality and
non-functionality of the system.
INFRASTRUCTURE:
RAM : 256 MB
Hard disk : 40 GB
26
StarUML
Microsoft Access
PROBLEM STATEMENT:
The system is built to be used by students and managed by a staff.
The student and staff have to login to the system before any processing can be done.
The student can see their marks report.
The administrator can maintain the student mark system and update it.

The modules of Student Mark Analyzing System is an integrated system that as four modules as part of
LOGIN FORM:
The student and administrator should login before any process done. The student can login by
his/her unique ID and Password to view their mark details.
STUDENT DETAILS:
The students must provide all his details to check the mark report. The details about students are
stored in the database.
GRADE CALCULATION:
The student grade is calculated based on the percentage of the subject.
DATA MODELING:
Data modeling provides detail about the system design or blue print of the Student Mark Analyzing
Use Case Diagram
Class Diagram
Activity Diagram
Sequence Diagram
State Diagram
Deployment Diagram
Component Diagram
Package Diagram
27
USE CASE DIAGRAM:
CLASS DIAGRAM:
28
ACTIVITY DIAGRAM:
STATE DIAGRAM:
29
DEPLOYMENT DIAGRAM:
SEQUENCE DIAGRAM:
30
COMPONENT DIAGRAM
31
PACKAGE DIAGRAM:
LOGIN
DOMAIN LAYER
STUDENT DETAILS MARKS DETAILS
TECHNICAL LAYER
DATA BASE
FORM1
ADMIN/LOGIN:
Private Sub Command1_Click()
If Text1.Text = "admin" Then
MsgBox "welcome to details form"
Form2.Show
Else
32
MsgBox" incorrect password"
End If
Else
MsgBox "incorrect User name"
End If
Text1.Text = ""
Text2.Text = ""
End Sub
CANCEL:
Unload Me
End Sub
STUDENT DETAIL
CLEAR:
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
End Sub
33
EXIT:
Unload Me
End Sub
LOAD:
Private Sub Form_Load()
Set DataGrid1.DataSource = Adodc1
DataGrid1.Refresh
End Sub
PERCULATION OF STUDENTS:
CLEAR:
Private Sub CLEAR_Click()
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text7.Text = ""
Text8.Text = ""
34
Text9.Text = ""
End Sub
CALCULATE:
Private Sub CALCULATE_Click()
eng = Val(Text3.Text)
mat = Val(Text4.Text)
phy = Val(Text5.Text)
chem = Val(Text6.Text)
cmp = Val(Text7.Text)
tot = eng + phy + chem + cmp + mat
avg = tot / 5
Text8.Text = tot
Text9.Text = avg
If avg> 75 Then
MsgBox "DISTINTION"
ElseIfavg> 60 Then
MsgBox "FIRST CLASS"
ElseIfavg> 50 Then
MsgBox "SECOND CLASS"
End If
End Sub
EXIT:
Private Sub EXIT_Click()
End
End Sub
35
RESULT:
Thus the project Student Mark Analyzing System was developed using STARUML software is done and
code generated successfully.
36
EX.NO.8
ONLINE TICKET RESERVATION SYSTEM
AIM:
To implement the Online Ticket Reservation System project using StarUml and Visual Basic.

In the E-Ticketing system the main process is a applicant have to login the database then the database
verifies that particular username and password then the user must fill the details about their personal details then
selecting the flight and the database books the ticket then send it to the applicant then searching the flight or else
cancelling the process.
OBJECTIVES:
The applicant should login to the database for reserving the ticket.
SCOPE:
In the specification use define about the system requirements that are part from the functionality of the
system. It tells the usability, reliability defined in the use case specification.
INFRASTRUCTURE:
RAM : 256 MB
Hard disk : 40 GB
StarUML
Microsoft Access
37
PROBLEM STATEMENT:
An online Ticket reservation system is software that helps in reservation of airline tickets in the internet
and check for the availability of tickets. This system shows all the information about all the transport services
including their source and destination, and the time of arrival and departure of all flights and the availability of
seats in all the flights. This system also has the facility of cancellation of tickets. If the tickets are not available
then the current status of the system also known through this system. The online reservation system maintains
the full details of the entire passenger who are reserving the tickets in the specified airline services.

The modules of online ticket reservation system is an integrated system that as four modules as part of
PASSENGER:
One who reserve tickets for traveling in the specified airline services.
ADMINISTRATOR:
One who books the tickets for the passenger needs and cancel the tickets, if the passenger
doesnt need it or cancellation of their trip. Administrator maintains all the details in the airline
and passenger database.
DATABASE:
One which stores the details of the arrival and departure of the airlines. It also stores the details
of the passenger who were booked the ticket for the specific airlines. It also stores the current
status of the ticket in the specified airlines.
DATA MODELING:
Data modeling provides detail about the system design or blue print of the online ticket reservation
Use Case Diagram
Class Diagram
Activity Diagram
Sequence Diagram
State Diagram
Deployment Diagram
Component Diagram
38
Package Diagram
USE CASE DIAGRAM:
CLASS DIAGRAM:
39
ACTIVITY DIAGRAM:
ADMIN LOGIN:
ADMIN
USERNAME/PASSWORD
YES NO
VALID INVALID
FLIGHT DETAILS:
USER
FLIGHT DETAILS
YES NO
DETAILS NO DETAILS FOUND
40
AVAILABILITY:
USER/ADMIN
AVAILABILITY
AVAILABLE SEATS SEATS FILLED
RESERVATION/CANCELLATION:
41
STATE DIAGRAM:
DEPLOYMENT DIAGRAM:
42
SEQUENCE DIAGRAM:
ADMIN LOGIN:
FLIGHT DETAILS:
43
AVAILABILITY:
RESERVATION / CANCELLATION:
44
COLLABORATION DIAGRAMS:
ADMIN LOGIN:
FLIGHT DETAILS:
AVAILABILITY:
45
RESERVATION/CANCELLATION:
COMPONENT DIAGRAM:
46
PACKAGE DIAGRAM:
LOGIN
DOMAIN LAYER
AVAILABILITY RESERVE / CANCEL
TECHNICAL LAYER
DATA BASE

FORM1
ADMIN:
Private Sub Command1_Click ()
If Text1.Text = "ADMIN" And Text2.Text = "ADMIN" Then
Frame1.Visible = True
Else
MsgBox "INVALID USERNAME AND PASSWORD"
End If
End Sub
47
PASSENGER DETAILS:
Form2.Show
End Sub
FLIGHT DETAILS:
Form3.Show
End Sub
EXIT:
End
End Sub
FORM 2:
FLIGHT DETAILS:
DataGrid1.Refresh
End Sub
48
Form4.Show
End Sub
FORM 3:
PASSANGER DETAILS:
End
End Sub

DataGrid1.Refresh
End Sub
49
RESULT:
Thus the project Online Ticket Reservation System was developed using STARUML software is done
and code generated successfully.
50
EX.NO.9
PLATFORM ASSIGNMENT SYSTEM FOR THE TRAINS IN A RAILWAY
STATION
AIM:
To implement the Platform assignment system for the trains in a railway station project using StarUml
and Visual Basic.

In the Platform assignment system for the trains in a railway station project the main process is a
applicant have to login the database then the database verifies that particular username and password then the
user must fill the details about their personal details then selecting the trains and enquiry about trains details &
delay calculated is calculated by database & then finally platform assigned.
OBJECTIVES:
The system is developed to reserve the ticket for the trains in a railway station.
SCOPE:
INFRASTRUCTURE:
RAM : 256 MB
Hard disk : 40 GB
StarUML
Microsoft Access
51
PROBLEM STATEMENT:
This project is about the platform assignment system for the train in railway station. It Contains 3
modules. The first module gets the current time, schedule time of the train and expected time that train could
enter into the station, departure time and platform number. Current time and schedule time is used to calculate
the time delay of the train. If the time delay is more than the specified time also is arrival time and platform
number of next train gets clashed then next train cannot be allowed into the same platform.

The modules of Platform assignment system for the trains in a railway station is an integrated system
that as four modules as part of it. The modules are as follows
LOGIN:
Basic flow: To authenticate the user, admin has to enter the username and password.
Alternate Flow: If password is wrong it will ask the admin to answer the security question
and retrieve the password.
Precondition: the system will ask the admin to enter the password
Post Condition: On success, the admin displays the admin information.
TRAIN DETAILS:
Basic flow: The train details like train number, schedule time, expected time to arrive, schedule time for
the departure, expected time to arrive.
Alternate Flow: If train is not correct the admin will report it.
Precondition: The train details should be known.
Post Condition: After verifying all the details the admin will move to next stage
DELAY CALCULATION:
Basic flow: The entered details are verified with the database and time delay is calculated and
also checks whether there is any clash with the next train timing.
Alternate Flow: If details are incorrect error message is generated.
Precondition: The detail of the database is up to date.
Post Condition: After verification the platform assignment is done.
PLATFORM ASSIGNMENT:
Basic flow: Based on the delay and arrival of the next train the platform assignment is done.
52
Alternate Flow: If no platform is free then the train is made to wait.
Precondition: The availability of the platform is known.
Post Condition: The platform is conformed and the signal is given for the train to stop.
DATA MODELING:
Data modeling provides detail about the system design or blue print of the Platform assignment system
for the trains in a railway station. It is represented by UML diagrams. Data modeling consists of
Use Case Diagram
Class Diagram
Activity Diagram
Sequence Diagram
State Diagram
Deployment Diagram
Component Diagram
Package Diagram
USE CASE DIAGRAM:
53
CLASS DIAGRAM:
ACTIVITY DIAGRAM:
54
STATE DIAGRAM:
DEPLOYMENT DIAGRAM:
55
SEQUENCE DIAGRAM:
56
COMPONENT DIAGRAM:
PACKAGE DIAGRAM:
LOGIN
DOMAIN LAYER
TRAIN & DELAY ALLOCATION OF

DETAILS PLATFORM
TECHNICAL LAYER
DATA BASE

FORM1
LOGIN:
Private Sub LOGIN_Click()
57
Form2.Show
Else
End If
Else
End If
Text1.Text = ""
Text2.Text = ""
End Sub
CANCEL:
Private Sub CANCEL_Click()
Unload Me
End Sub
FORM 2:
TRAIN DETAILS:
Dim db As DAO.Database
Dim rs As DAO.Recordset
58
CANCEL:
Unload Me
End Sub
LOAD:
Set db = OpenDatabase("C:\Users\Administrator\Documents\train.mdb")
Set rs = db.OpenRecordset("TRAINDETAILS", dbOpenDynaset)
End Sub
NEXT:
Private Sub NEXT_Click()
Adodc1.Recordset.MoveNext
End Sub
PREVIOUS:
Private Sub PREVIOUS_Click()
Adodc1.Recordset.MovePrevious
End Sub
FORM 3:
DELAY CALCULATIONS:
59
Dim str, str1, str2 As Double
CALCULATE:
Private Sub CALCULATE_Click()
str = Val(Text4.Text)
str1 = Val(Text3.Text)
str2 = str - str1
Text5.Text = str2
End Sub
CANCEL:
Unload Me
End Sub
LOAD:
Set db = OpenDatabase("C:\Users\Administrator\Documents\train.mdb")
Set rs = db.OpenRecordset("TRAINDETAILS", dbOpenDynaset)
End Sub
RESULT:
Thus the project Platform assignment system for the trains in a railway station was developed using
STARUML software is done and code generated successfully.
60
EX.NO.10
EXPERT SYSTEM TO PRESCRIBE THE MEDICINES FOR THE GIVEN
SYMPTOMS
AIM:
To implement the Expert system to prescribe the medicines for the given symptoms project using
StarUml and Visual Basic.

In the Expert system to prescribe the medicines for the given symptoms project, the patient can register
their details and get the details about disease & get solutions to cure the diseases. The patient can also complain
if the diseases not cured. The details about patients are stored in database and maintained securely for future
reference.
OBJECTIVES:
The expert system project is software which is used to maintain the patient details and the patients can
get the prescription for the specified deficiency.
SCOPE:
INFRASTRUCTURE:
RAM : 256 MB
Hard disk : 40 GB
StarUML
Microsoft Access
61
PROBLEM STATEMENT:
The expert system project is software which is used to maintain the patient details and the patients can
get the prescription for the specified deficiency. If the patients did not get cure then they can be fix an
appointment with the specialist of their deficiency disease. Some of the severe ills like heart attack, brain tumor
has been directly admitted as the inpatient. The patients can check their full details about their prescriptions and
stage of their disease are viewed directly through this software. The inpatient details are stored in the database
and have been retrieved when they needed using their login. Then the appointment fixing has been directly done
in the online method using the time table of the specialists

The modules of expert system is an integrated system that as four modules as part of it. The modules are
as follows
ADMIN LOGIN:
Basic Workflow: Specialist is provided with the username and password to login in to the
system.
Alternate Workflow: If the specialist enters the wrong username or password then the specialist
is blocked by the system.
Pre Condition: The specialist must have username and password allotted for him to access the
system.
Post Condition: The specialist is allowed to access the inpatient details and made the require
changes in the prescription and edit the health condition of the inpatients.
INPATIENT DETAILS:
Basic Workflow: The specialist gives the details to the receptionist, and then they will enter the
respective.
Alternate Workflow:NIL
Pre Condition: The specialist must give the patient details.
Post Condition: The receptionist enters the new prescription and edits the health condition of
the inpatients.
OUTPATIENT ACCESS:
Basic Workflow: The out patients access the system and get their prescription and can consult
the doctor by fixing an appointment in the same phase.
62
Alternate Workflow: NIL
Pre Condition: The outpatient must log on to the system.
Post Condition: The outpatients get their prescription and can fix an appointment for their
specified deficiency.
FIXING APPOINTMENT:
Basic Workflow: The receptionist is approached by the patients to see the specialist for their
disease.
Alternate Workflow: If the time schedule is busy, then the patients are asked to wait for a week.
Pre Condition: The specialist time schedule must be updated.
Post Condition: The receptionist fixes an appointment with the specialist which is specified by
the patients.
DATA MODELING:
Data modeling provides detail about the system design or blue print of the Expert system. It is
represented by UML diagrams. Data modeling consists of
Use Case Diagram
Class Diagram
Activity Diagram
Sequence Diagram
State Diagram
Deployment Diagram
Component Diagram
Package Diagram
CLASS DIAGRAM:
63
USE CASE DIAGRAM:
ACTIVITY DIAGRAM:
64
STATE DIAGRAM:
DEPLOYMENT DIAGRAM:
65
SEQUENCE DIAGRAM:
COMPONENT DIAGRAM:
66
PACKAGE DIAGRAM:
LOGIN
DOMAIN LAYER
PATIENT DETAILS DISEASE DETAILS
TECHNICAL LAYER
DATA BASE

FORM1
LOAD:
Frame1.Visible = False
End Sub
LOGIN:
MsgBox "WELCOME ADMIN!!!!!!!!!"
Else
67
End If
Else
End If
Text1.Text = ""
Text2.Text = ""
End Sub
CANCEL:
Unload Me
End Sub
FORM 2:
PATIENT DETAILS:
Private Sub PATIENTDETAIL_Click()
Form2.Show
End Sub
PRESCRIBE MEDICINE:
Private Sub PRESCRIBEMEDICINE_Click()
Form3.Show
End Sub
68
FORM 3:
PATIENT DETAILS:
ADD:
Private Sub ADD_Click()
Adodc1.Recordset.AddNew
End Sub
CANCEL
Unload Me
End Sub
CLEAR
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
End Sub
DELETE
Private Sub DELETE_Click()
Adodc1.Recordset.Delete
69
End Sub
LOAD:
DataGrid1.Refresh
Set db = OpenDatabase("C:\Users\Administrator\Documents\patient.mdb")
Set rs = db.OpenRecordset("PATIENT", dbOpenDynaset)
End Sub
NEXT:
End Sub
PREVIOUS:
End Sub
70
FORM 4:
PRESCRIBE MEDICINE:
ADD:
End Sub
CANCEL:
Unload Me
End Sub
CLEAR:
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
End Sub
DELETE:
End Sub
LOAD:
DataGrid1.Refresh
End Sub
NEXT:
71
End Sub
PREVIOUS:
End Sub
UPDATE:
Private Sub UPDATE_Click()
Adodc1.Recordset.Update
End Sub
RESULT:
Thus the project Expert system was developed using STARUML software is done and code generated
successfully.
72
EX.NO.11
REMOTE COMPUTER MONITORING
AIM:
To implement the Remote computer monitoring for monitoring the ECG of patient using StarUml and
Visual Basic.

In the Remote computer monitoring for monitoring the ECG of patient, the patient can register their
details and get the details about disease & get solutions to cure the diseases. The patient can also complain if the
diseases not cured. The details about patients are stored in database and maintained securely for future
reference.
OBJECTIVES:
The Remote computer monitoring project is software which is used to maintain the patient details and
the patients can get the prescription for the specified deficiency.
SCOPE:
INFRASTRUCTURE:
RAM : 256 MB
Hard disk : 40 GB
StarUML
Microsoft Access
73
PROBLEM STATEMENT:
The remote computer monitoring system project is software which is used to maintain the patient details
and the patients can get the history of ECG. ECG of the patient is monitored by the card recorder and will be
recorded if ECG of any patient goes wrong it will be intimated to the physician immediately and also the
emergency alarm is made to ring.

The modules of remote computer monitoring system is an integrated system that as four modules as part
of it. The modules are as follows
ADMIN LOGIN:
Basic Workflow: Specialist is provided with the username and password to login in to the
system.
Alternate Workflow: If the specialist enters the wrong username or password then the specialist
is blocked by the system.
Pre Condition: The specialist must have username and password allotted for him to access the
system.
Post Condition: The specialist is allowed to access the inpatient details and made the require
changes in the prescription and edit the health condition of the inpatients.
ECG RECORDER:
Basic Workflow: ECG recorder is monitoring the ECG of the patient.
Pre Condition: The ECG recorder has to monitor the ECG of patient if something goes wrong
he has to intimate immediately to the physician.
Post Condition: The physician is allowed to attend the patient and he should decide to continue
with same treatment or to change the treatment.
PATIENT:
One who get into the hospital as in/out patients and get an prescription from the specialists.
PHYSICIAN:
One who test the patients and give the prescription to the in/out patients.
74
DATA MODELING:
Data modeling provides detail about the system design or blue print of the remote computer monitoring
Use Case Diagram
Class Diagram
Activity Diagram
Sequence Diagram
State Diagram
Deployment Diagram
Component Diagram
Package Diagram
USE CASE DIAGRAM:
75
CLASS DIAGRAM:
ACTIVITY DIAGRAM:
76
STATE CHAT DIAGRAM:
DEPLOYMENT DIAGRAM:
77
SEQUENCE DIAGRAM:
78
COMPONENT DIAGRAM:
PACKAGE DIAGRAM:
LOGIN
DOMAIN LAYER
PATIENT DETAILS ECG REPORT
TECHNICAL LAYER
DATA BASE

FORM1
LOAD:
79
End Sub
LOGIN:
Else
End If
Else
End If
Text1.Text = ""
Text2.Text = ""
End Sub
CANCEL:
Unload Me
End Sub
80
FORM 2:
PATIENT DETAILS:
Private Sub PATIENTDETAIL_Click()
Form2.Show
End Sub
PRESCRIBE MEDICINE:
Private Sub PRESCRIBEMEDICINE_Click()
Form3.Show
End Sub
FORM 3:
PATIENT DETAILS:
ADD:
End Sub
CANCEL
Unload Me
End Sub
CLEAR
81
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
End Sub
DELETE
End Sub
LOAD:
DataGrid1.Refresh
End Sub
NEXT:
End Sub
PREVIOUS:
End Sub
82
FORM 4:
PRESCRIBE MEDICINE:
ADD:
End Sub
CANCEL:
Unload Me
End Sub
CLEAR:
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
83
Text4.Text = ""
End Sub
DELETE:
End Sub
LOAD:
DataGrid1.Refresh
End Sub
NEXT:
End Sub
PREVIOUS:
End Sub
UPDATE:
Private Sub UPDATE_Click()
End Sub
84
RESULT:
Thus the project Remote computer monitoring for monitoring the ECG of patient was developed using
STARUML software is done and code generated successfully.
85
EX.NO.12
ATM SYSTEM
AIM:
To implement the ATM System using StarUml and Visual Basic.

ATM Processing System is used by any user who wishes to withdraw amount. The user logs in. He/she
must fill up and submit the form. In this form he/she must specify the details and it is used to maintain the
balance limitation. This project allows the user to withdraw amount from any ATM system.
OBJECTIVES:
This document gives the detail functional and non functional requirements for the ATM monitoring
system. The purpose of this document is that the requirements mentioned in it should be utilized by the software
developer to implement the system.
SCOPE:
The system allows to access the bank. The system display login form. After submitting the form along
with the account details, the user balance limitation is checked depending upon the bank balance of the user, all
the process is done.
INFRASTRUCTURE:
RAM : 256 MB
Hard disk : 40 GB
StarUML
Microsoft Access
86
PROBLEM STATEMENT:
An ATM System is software which is used to perform and maintain the banking details of each and
every customer. The ATM System keeps track of the transaction done at any time by the customer and it also
reduces time for procedural time for transaction. It allows complete security to the bank details with the pin
number provided by the bank to the customer. The user can check the balance, withdraw or deposit the money.
The customer can access and get their full benefits of the bank at any time using this software. This system will
check for the exact pin number when the card is inserted into the machine and then transactions are made.

The modules of ATM system is an integrated system that as four modules as part of it. The modules are
as follows
ADMIN LOGIN:
Basic Workflow: Customer inserts the ATM card and systems request for pin number. After
customer entering the correct user name and details the system gives access to the customer to
work with their balance.
Alternate Flow: If the customer enters invalid pin number then display the message invalid
type.
Pre Condition: Customer must have ATM card with him.
Post Condition: Customer is given access to the system to do their transaction.
WITH DRAW:
Basic Workflow: Customer enters the amount to be withdrawn from his account. If the
withdrawing amount is lesser than the balance of his account then the cash is issued.
Alternate Flow: If the customer enters the amount which is greater than the balance of his
account then the system displays the error message.
Pre Condition: Customer should be logged on to the ATM system.
Post Condition: System issues the cash to the customer.
DEPOSIT:
Basic Workflow: Customer enters the amount to be deposited to his account. Then the system
gets the amount from the customer and deposit in his account.
Alternate Flow: NIL
87
Post Condition: Customer deposits the amount in his account.
BALANCE ENQUIRY:
Basic Workflow: Customer enters the pin number for checking his balance.
Alternate Flow: NIL
Post Condition: System shows the balance amount of the customer.
PIN CHANGE:
Basic Workflow: Customer enters the old pin number and the new pin number for changing his
pin number. System analyses his old pin, if it is correct then it changes the account pin number to
the entered new pin number.
Alternate Flow: If the customer enters the wrong pin number then the system displays the error
message.
Post Condition: System changes the pin number of the customers account.
USER DETAILS:
Basic Workflow: Customer enters the user ID to the system. Then the system shows the details
of the currently logged customer.
Alternate Flow: NIL
Post Condition: System displays the details of the customer.
DATA MODELING:
Data modeling provides detail about the system design or blue print of the ATM system. It is
Use Case Diagram
Class Diagram
Activity Diagram
Sequence Diagram
88
State Diagram
Deployment Diagram
Component Diagram
Package Diagram
USE CASE DIAGRAM:
CLASS DIAGRAM:
89
ACTIVITY DIAGRAM:
STATE CHAT DIAGRAM:

insert the enter pin
card No .
check pin reverse pin no.

no.
correct pin no.
withdraw police
amount
wrong pin number
show acc
take card
90
DEPLOYMENT DIAGRAM:
ATM server
customer
ATMmachine
SEQUENCE DIAGRAM:
: Machine Atm_Server
Custom
er Insert
card
Request pin
Pin number
Pin check
Acknowledgement
Choose Account
Check
Display
Balance
Details
Withdraw amount
Insufficient balance
Amount
Reciept
91
1: Insert card
3: Pin number
6: Choose Account
9: Balance Machine
11: Withdraw amount
2: Request pin
13: Amount
4: Pin check
5: Acknowledgement 7: Check
customer
8: Display
10: Details
12: Insufficient balance
Atm_Ser
14: Reciept
ver
COMPONENT DIAGRAM:
card pin account
Current Savings
account account
reciept withdraw
92
PACKAGE DIAGRAM:

FORM1
LOGIN:
Data1.Recordset.AddNew
MsgBox "Login Successful"
Form2.Show
End Sub
CANCEL:
MsgBox "Take Your Card"
93
Form5.Show
End Sub
FORM 2:
WITHDRAW:
Form3.Show
End Sub
CANCEL:
Form1.Show
End Sub
94
FORM 3:
OK:
Data2.Recordset.AddNew
MsgBox "Collect your amount"
End Sub
CANCEL:
Form2.Show
End Sub
FORM 4:
Click:
Form1.Show
End Sub
95
RESULT:
Thus the project ATM System was developed using STARUML software is done and code generated
successfully.
96
EX.NO.13
STOCK MAINTENANCE SYSTEM
AIM:
To implement the Stock Maintenance System using StarUml and Visual Basic.

The Stock Maintenance System, initial requirement to develop the project about the mechanism of the
Stock Maintenance System is caught from the customer. The requirement are analyzed and refined which
enables the end users to efficiently use Stock Maintenance System. The complete project is developed after the
whole project analysis explaining about the scope and the project statement is prepared.
OBJECTIVES:
The main objective of the stock maintenance system is to maintain the stock. It provides the vendor to
maintain the stock in a precise manner.
SCOPE:
The overview of the project is to design an online tool for the recruitment process which eases the work
for the customer as well as the companies. Companies can create their company forms according to their wish
in which the applicant can register.
INFRASTRUCTURE:
RAM : 256 MB
Hard disk : 40 GB
StarUML
Microsoft Access
97
PROBLEM STATEMENT:
A Stock Maintenance System is a software project used to maintain the stock details of a Super Market.
In this project it has a useful scenario which is used to know the available details of the product of the super
market by the customer. This project keeps tracks of the product sales of the super market. This project alerts
the super visor of the super market for less quantity products availability or if any product is not available in the
super market. This project allows the customer to view the availability of any product and it shows the rate of
the product. This project allows the supervisor to set price for the product.

as follows
USER:
Basic Workflow: Customer is requesting the system for knowing the details of the product
which is currently available in the super market.
Alternate Workflow: If the products are not available in the super market then it displays the
error message.
Pre Condition: The system must display the list of products available in the super market to the
customer.
Post Condition: Customer had purchased the products from the super market.
ADMIN LOGIN:
Basic Workflow: Supervisor is provided with the username and password to login in to the
system.
Alternate Workflow: If the supervisor enters the wrong username or password then the admin is
blocked by the system.
Pre Condition: The supervisor must have username and password allotted for him to access the
system.
Post Condition: The supervisor is allowed to do changes in the stock availability of the super
market.
98
DEPOSIT:
Brief Description: This use case allows the supervisor to keep track of information about the
products availability, rate, and etc..,
Basic Workflow: Admin has a control for editing the various activities of the product
management and maintains the record in the database.
Pre Condition: The supervisor must log on to the system.
Post Condition: The changes of the product characteristics have been updated.
DATA MODELING:
Data modeling provides detail about the system design or blue print of the Stock Maintenance system. It
is represented by UML diagrams. Data modeling consists of
Use Case Diagram
Class Diagram
Activity Diagram
Sequence Diagram
State Diagram
Deployment Diagram
Component Diagram
Package Diagram
USE CASE DIAGRAM:
99
CLASS DIAGRAM:
USER OPTION:
ADMIN LOGIN:
ADMIN MANAGEMENT:
ACTIVITY DIAGRAM:
100
ADMIN MAINTENANCE
USER OPTIONS
101
SEQUENCE DIAGRAMS:
ADMIN LOGIN:
USER OPTIONS:
ADMIN MAINTANCE:
102
ADMIN LOGIN:
USER OPTION:
ADMIN MAINTANANCE:
103
STATE CHAT DIAGRAM:
DEPLOYMENT DIAGRAM:
COMPONENT DIAGRAM:
104
PACKAGE DIAGRAM:

FORM1
LOGIN:
Private Sub login_Click()
If Text2.Text = "Admin" Then
Form2.Show
Else
MsgBox " incorrect password"
End If
Else
End If
Text1.Text = ""
Text2.Text = ""
End Sub
105
CANCEL:
Private Sub Cancel_Click()
Unload Me
End Sub
FORM 2:
CHOICE:
Unload Me
Form1.Show
End Sub

Form3.Show
End Sub
Private Sub bill_Click()

Form4.Show
End Sub
Private Sub cancel_home_Click()

Unload Me
Form1.Show
End Sub
Private Sub display_Click()
106
Form3.Show
Form3.Edit.Visible = False
Form3.new.Visible = False
End Sub
Private Sub new_edit_Click()

Form3.Show
End Sub
Private Sub search_Click()

Form3.Show
End Sub
FORM 3:
DETAILS:
Dim str As String

Unload Me
End Sub
Private Sub Clear_Click()

Clear1
End Sub
107
End Sub
Private Sub edit_Click()

Adodc1.Refresh
Reload
End Sub

Set db = OpenDatabase("C:\Users\Administrator\Documents\trade.mdb")
Set rs = db.OpenRecordset("item_details", dbOpenDynaset)
End Sub
Private Sub new_Click()

rs.AddNew
rs.Fields("Item no") = Val(Text1.Text)
rs.Fields("Item name") = Text2.Text
rs.Fields("Quantity") = Val(Text3.Text)
rs.Fields("MFD") = Format(Val(Text4.Text), "DD/MM/YYYY")
rs.Fields("ED") = Format(Val(Text5.Text), "DD/MM/YYYY")
rs.Fields("MRP") = Val(Text6.Text)
rs.Update
MsgBox " Data's are inserted"
Reload
Clear1
End Sub
Public Sub Reload()

Adodc1.Refresh
End Sub
108
Public Sub Clear1()
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
End Sub
Private Sub next_Click()

End Sub
Private Sub Prev_Click()

rs.MovePrevious
If rs.BOF Then
MsgBox " this is first record"
rs.MoveFirst
End If
Text1.Text = rs.Fields("Item no")
Text2.Text = rs.Fields("Item name")
Text3.Text = rs.Fields("quantity")
Text4.Text = rs.Fields("MFD")
Text5.Text = rs.Fields("ED")
Text6.Text = rs.Fields("MRP")
End Sub
109
FORM 4:
BILLING DETAILS:
Dim str, str1, str2, dis As Long

str2 = str1 + ((str1 * 10) / 100)
If str2 > 1000 Then
dis = str2 * 0.01
str2 = str2 - dis
Text5.Text = dis
Else
Text5.Text = 0
End If
Text7.Text = str2
End Sub

Unload Me
110
Form2.Show
End Sub
Private Sub Continue_Click()

str = Val(Text3.Text) * Val(Text4.Text)
str1 = str1 + str
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
str = 0
End Sub

str = 0
str1 = 0
End Sub
RESULT:
Thus the project Stock Maintenance System was developed using STARUML software is done and code
generated successfully.
111
EX.NO.14
QUIZ SYSTEM
AIM:
To implement the Quiz System using StarUml and Visual Basic.

The quiz system project is software which is used to test the general knowledge power of the user. Quiz
system acts as a good brain teaser for the users. In the quiz system, the main concept is that it will create a good
creativity and it helps the user to get knowledge of the current world affairs, history and etc.
OBJECTIVES:
The main objective of the quiz system project is software which is used to test the general knowledge
power of the user
SCOPE:
The scope of the project is to design an online quiz system, that will help the student to write the quiz in
a easier manner, which also helps the student to test their capability.
INFRASTRUCTURE:
RAM : 256 MB
Hard disk : 40 GB
StarUML
Microsoft Access
112
PROBLEM STATEMENT:
This quiz system consists of four rounds. In each and every round there is a different set of questions
and there may be allocation of marks in each round. There is a minimum marks to be scored in each and every
round, if the user may scoreless then the user must logged out of the software. The user is specified with a
username and password, so that the individual details can be stored in the database.

as follows
USER LOGIN:
Basic Workflow: User is provided with the unique username and password to login in to the
system.
Alternate Workflow: If the user enters the wrong username or password then the user is
blocked by the system.
Pre Condition: The user must have username and password allotted for him to access the
system.
Post Condition: The user is allowed to attend the various rounds in the quiz system.
ROUNDS:
Basic Workflow: User is specified with a set of questions, so that he answers all the questions in
each round.
Pre Condition: The user must log on to the system.
Post Condition: The user is allowed to attend the various rounds in the quiz system.
EVALUTION:
Basic Workflow: System is allowed to evaluate the user answer and assign marks according to
their answers.
Pre Condition: The system is allowed to check the user answers after finishing the rounds.
Post Condition: The system allocates the marks to the user and if it is less then minimum marks
then the user is invalid to continue the next round.
113
DATA MODELING:
Data modeling provides detail about the system design or blue print of the Quiz system. It is represented
by UML diagrams. Data modeling consists of
Use Case Diagram
Class Diagram
Activity Diagram
Sequence Diagram
State Diagram
Deployment Diagram
Component Diagram
Package Diagram
USE CASE DIAGRAM:
CLASS DIAGRAM:
114
ACTIVITY DIAGRAM:
USER LOGIN:
ROUNDS:
EVALUATION:
115
SEQUENCE DIAGRAMS:
USER LOGIN:
ROUNDS:
EVALUATION:
116
USER LOGIN:
ROUNDS:
EVALUTION:
117
STATE CHAT DIAGRAM:
DEPLOYMENT DIAGRAM:
118
COMPONENT DIAGRAM:
PACKAGE DIAGRAM:
LOGIN
DOMAIN LAYER
USER DETAILS ROUNDS & RESULTS
TECHNICAL LAYER
DATA BASE
119
FORM1
LOGIN:
If Text1.Text = "" And Text2.Text = "" Then
RULES.Show
Else
MsgBox "INVALID PASSWORD"
End If
End Sub
FORM 2:
ROUND 1:
Dim C As Integer
C=C+1
Label3.Visible = True
Command3.Visible = True
End Sub

C=C+1
120
End Sub

C=C+1
End Sub

C=C+0
End Sub

C=C+0
End Sub

C=C+1
End Sub
121
C=C+1
End Sub

C=C+0
End Sub

C=C+1
End Sub

C=C+0
End Sub

C=C+0
Text1.Text = C * 5
End Sub
122
C=C+0
End Sub

C=C+1
Text1.Text = C * 5
End Sub
If Val(Text1.Text) >= 30 Then
R2.Show
Else
Unload Me
End If
End Sub

C=C+1
End Sub

C=C+0
End Sub
123
C=C+1
End Sub

C=C+0
End Sub

C=C+0
End Sub

C=C+1
End Sub

C=C+0
124
End Sub

Label3.Visible = False
Command3.Visible = False
End Sub
125
FORM 3:
ROUND 2:
Dim D As Integer

If Text1.Text = "34" Then
D=D+1
Else
D=D+0
End If
If Text2.Text = "WI" Then
D=D+1
Else
D=D+0
End If
If Text3.Text = "LARA" Then
D=D+1
Else
D=D+0
126
End If
If Text4.Text = "1996" Then
D=D+1
Else
D=D+0
End If
If Text5.Text = "BHUTIA" Then

D=D+1
Else
D=D+0
End If
Text6.Text = D * 10
If Val(Text6.Text) >= 40 Then
R3.Show
Else
Unload Me
End If
End Sub

End Sub
127
FORM 4:
ROUND 3:
Dim str, str1, str2, dis As Long

str2 = str1 + ((str1 * 10) / 100)
If str2 > 1000 Then
dis = str2 * 0.01
str2 = str2 - dis
Text5.Text = dis
Else
Text5.Text = 0
End If
Text7.Text = str2
End Sub

Unload Me
Form2.Show
End Sub
Private Sub Continue_Click()

str = Val(Text3.Text) * Val(Text4.Text)
str1 = str1 + str
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
str = 0
End Sub
128
str = 0
str1 = 0
End Sub
FORM 5:
RULES:
R1.Show
End Sub
129
FORM 6:
TOTAL:
Text1.Text = Val(R1.Text1.Text)
Text4.Text = Val(Text1.Text) + Val(Text2.Text) + Val(Text3.Text)
End Sub

Unload Me
End Sub
RESULT:
Thus the project Quiz System was developed using STARUML software is done and code generated
successfully.
130
EX.NO.15
EMAIL - CLIENT SYSTEM
AIM:
To implement the Email-Client System using StarUml and Visual Basic.

The email client system is designed to send the message to another person at any time to share his/her
messages. This is very useful for user to deliver message easily. Each and every user must have unique ID and
Password. New users can sign up to create a id and existing user can sign in to access the email account with
correct id password.
OBJECTIVES:
The main purpose of creating the document about the software is to know about the list of the
requirement in the software project part of the project to be developed.
SCOPE:
In this specification, we define about the system requirements that are about from the functionality of
the system. It tells the users about the reliability defined in use case specification.
INFRASTRUCTURE:
RAM : 256 MB
Hard disk : 40 GB
StarUML
Microsoft Access
131
PROBLEM STATEMENT:
The goal of system analysis is to determine where the problem is in an attempt to fix the system. The
step involves breaking down the system into different pieces to analyses the solution, analyses project goals,
breaking down what needs to be created and attempting to engage users so that definite requirements can be
defined.

The modules of Email Client system is an integrated system that as four modules as part of it. The
modules are as follows
AUTHORIZATION:
The user enters a user name and password.
If it is valid, the users account becomes available.
If it is invalid, an appropriate message is displayed to the user.
INBOX:
The Inbox use case is used to view the mails that are received.
The user logs in by specifying the email id and password.
User selects the inbox option to view and the mails.
The user can also do the delete operation.
COMPOSE MAIL:
This use case is used to create and send mail it to the recipient.
The user signs in by specifying the email id and password.
The user selects compose mail option.
The recipient mail id and message are entered.
The user may send the mail or save it to the draft.
SEND MAIL:
This use case is use to send the mail after composing it.
It asks about the subscriber mail id and subject about the mail.
132
OUTBOX:
The sent mail use case is used to view the mail send from the users account.
The user signs in by specifying the email id and password.
The user selects the send mail option.
The user sent mail is shown.
DATA MODELING:
Data modeling provides detail about the system design or blue print of the Email-Client System. It is
Use Case Diagram
Class Diagram
Activity Diagram
Sequence Diagram
State Diagram
Deployment Diagram
Component Diagram
Package Diagram
USE CASE DIAGRAM:
133
CLASS DIAGRAM:
ACTIV
ITY
DIAGR
AM
134
SEQUENCE DIAGRAMS
135
COLLOBRATION DIAGRAM:
STATE CHAT DIAGRAM:
DEPLOYMENT DIAGRAM:
136
COMPONENT DIAGRAM:
PACKAGE DIAGRAM:
LOGIN
DOMAIN LAYER
USER DETAILS MAIL SYSTEM
TECHNICAL LAYER
DATA BASE
137
FORM1
CANCEL:
Unload Me
End Sub
LOGIN:
If Text1.Text = "ADMIN" Then
If Text2.Text = "ADMIN" Then
Form2.Show
Else
MsgBox " incorrect password"
End If
End If
End Sub
FORM 2: OPTION
CANCEL:
Unload Me
138
End Sub
COMPOSE:
Private Sub COMPOSE_Click()
Form4.Show
End Sub
INBOX:
Private Sub INBOX_Click()
Form3.Show
End Sub
FORM 3: INBOX
CANCEL:
End
End Sub
COMPOSE:
Private Sub COMPOSE_Click()
Form4.Show
End Sub
139
LOAD:
DataGrid1.Refresh
End Sub
FORM 4:COMPOSE
CANCEL:
End
End Sub
SEND:
Private Sub SEND_Click()
MsgBox "MESSAGE SENT SUCCESSFULLY"
End Sub
140
RESULT:
Thus the project Email - Client System was developed using STARUML software is done and code
generated successfully.
141

Project - Software Engineering Techniques

Uploaded by

Document Information

Original Description:

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

Project - Software Engineering Techniques

Uploaded by

Copyright:

Available Formats

EX.

SOFTWARE REQUIREMENTS ANALYSIS:

ISSUES OF PROJECT PLAN:

STEPS IN THE REQUIREMENTS ANALYSIS PROCESS

II. Identify the customer

III. Requirements elicitation

ADVANTAGES OF DATA MODELING:

STATIC AND DYNAMIC DATA MODELING:

MODELING A SYSTEMS ARCHITECTURE

UML PRIMARY GOALS:

PROBLEM ANALYSIS AND PROBLEM PLANNING:

SOFTWARE REQUIREMENT ANALYSIS:

USE CASE DIAGRAM:

USER INTERFACE LAYER

STUDENT DETAILS REGISTRATION

SYSTEM DESIGN AND IMPLEMENTATION:

Private Sub update_Click()

PROBLEM ANALYSIS AND PROBLEM PLANNING:

SOFTWARE REQUIREMENT ANALYSIS:

USER INTERFACE LAYER

STUDENT DETAILS MARKS DETAILS

SYSTEM DESIGN AND IMPLEMENTATION:

PROBLEM ANALYSIS AND PROBLEM PLANNING:

SOFTWARE REQUIREMENT ANALYSIS:

DETAILS NO DETAILS FOUND

AVAILABLE SEATS SEATS FILLED

USER INTERFACE LAYER

AVAILABILITY RESERVE / CANCEL

SYSTEM DESIGN AND IMPLEMENTATION:

Private Sub Form_Load()

PROBLEM ANALYSIS AND PROBLEM PLANNING:

SOFTWARE REQUIREMENT ANALYSIS:

USE CASE DIAGRAM:

USER INTERFACE LAYER

TRAIN & DELAY ALLOCATION OF

SYSTEM DESIGN AND IMPLEMENTATION:

PROBLEM ANALYSIS AND PROBLEM PLANNING:

SOFTWARE REQUIREMENT ANALYSIS:

USER INTERFACE LAYER

PATIENT DETAILS DISEASE DETAILS

SYSTEM DESIGN AND IMPLEMENTATION:

PROBLEM ANALYSIS AND PROBLEM PLANNING:

SOFTWARE REQUIREMENT ANALYSIS:

USE CASE DIAGRAM:

USER INTERFACE LAYER

PATIENT DETAILS ECG REPORT

SYSTEM DESIGN AND IMPLEMENTATION:

PROBLEM ANALYSIS AND PROBLEM PLANNING:

SOFTWARE REQUIREMENT ANALYSIS:

USE CASE DIAGRAM:

STATE CHAT DIAGRAM:

check pin reverse pin no.

correct pin no.

card pin account

SYSTEM DESIGN AND IMPLEMENTATION:

PROBLEM ANALYSIS AND PROBLEM PLANNING:

SOFTWARE REQUIREMENT ANALYSIS:

USE CASE DIAGRAM:

SYSTEM DESIGN AND IMPLEMENTATION:

Private Sub Command1_Click()

Private Sub bill_Click()

Private Sub cancel_home_Click()

Private Sub display_Click()