Software Engineering 120421 PDF
Software Engineering 120421 PDF
Software Engineering
(22413)
Semester –IV
Maharashtra State
Board of Technical Education, Mumbai
(Autonomous) (ISO 9001 : 2015) (lSO/IEC 27001 : 2013)
Maharashtra State Board of Technical Education,
(Autonomous) (ISO 9001 : 2008) (lSO/IEC 27001 : 2005)
4th Floor, Government Polytechnic Building, 49, Kherwadi, Bandra ( East ), Mumbai
400051.
(Printed on December, 2018)
MAHARASHTRA STATE
Certificate
This is to certify that Mr. /
Ms:……………………………………………………………..............
in……………………………….................................................................................................... of
completed the term work satisfactorily in course - Software Engineering (22413) for the
academic year 20…. - 20…… as Prescribed in curriculum
Prepare USE Cases and and Draw Use Case Diagram using
5 CO2 PrO5
modelling Tool
7 CO3 PrO7 Develop data Designs using DFD Decision Table & ER
PRATICAL -1
Write Problem statement to define the Project Title with bounded scope of the project.
…WRITE PROBLEM STATEMENT TO DEFINE THE PROJECT TITLE WITH BOUNDED SCOPE OF
THE PROJECT.
I] PRATICAL SIGNIFICANCE
To analyze the basic requirement of software product and to generate problem statement and to
analyze the bounded scope of the software product.
V] PRACTICAL OUTCOMES:-
Write a problem statement to define the perfect title the perfect title with bounded scope of
the project.
VI] RELEVANT AFFECTIVE DO MAIN RELATED OUTCOMES:-
A problem statement is clear consist description of the issue that needs to be addressed by
a problem solving team. It is used to center and focus the team at the beginning keep the team on track
during the effects delivered on outcomes that solves the problem statement.
➢ How to write problem statement: - Write down your vision to in order to decided what must,
be done while, solving. The pattern it‟s important to understand the vision. It‟s an initial
starting point for a project. A problem statement expressed the words that will be used to keep
the efforts focused and it should represent a solvable problem. The file can be used to spark the
discussion about the problem.
1) How to write a program statement.
2) How to get it started.
3) Who does the problem affect?
4) What are the boundaries of the problem?
5) When the issue does occurs.
6) Where is the issue programming.
7) Why it is important to fix the program.
XI] CONCLUSION
THUS,WE HAVE TO PERFROMED PRACTICAL SUCCESFULLY
XII] EXERCISE:
1.ANS
2.ANS
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………
………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
j
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
XIII] REFERENCES:-
2) http://www.google.com
3) http://softwarebaba.com
4) Software Engineering by press man
Process Product
Total(25)
Related(7.5) Related(17.5)
PRATICAL -2
Select relevant process model of define activities & related tasks set of assignment project.
I] PRATICAL SIGNIFICANCE
To select and analyze the relevant model for assigned project and to define activities and related tasks set for
assigned project.
Po4 - Communication.
Write a program statement to define project. Project title with bounded scope the project.
PROCESS MODEL:-
A software process model is define simplified process representation of software process each methods
represent a process from a specific perspective.
WATERFALL MODEL:-
The waterfall model is also called as ' the linear-sequential model ' or ' classic life ' cycle model. The software
development starts with requirements gathering phase. Then progress through analysis, design, coding, testing
& maintenance.
Fig: Water fall Model
VII] CONCLUSION:
THUS,WE HAVE UNDERSTAND THE PROCESS MODEL AND TASKS SET OF ASSIGNMENT.…
VIII] EXERCISE:
• MAINTAINCE- is fixing issues and release new version with the issues patches are required.
2.ANS-
A process framework established the foundation for a complete software process by identifying a small
number of framework activities that are capable to all software projects
COMMUNICATION- in this activity heavy communication with customers and other stakeholders
PLANNING- in this activity we discuss the technical related tasks, work, schedule, risk,requirements etc
MODELING- modelling is about building representation of things in the real world
CONSTRUCTION- in software engineering construction is a set of procedures that are needed to assemble
the product.
3.ANS:
A software process model is an abstraction of the software development process the model specified the
stages and order of a process so think of this as a representation of the order of activities of the process and
the sequence in which they are performed.
A model well defined the following.
• The tasks to be performed
• The input and output of each task
• The pre and post conditions for each task
• The flow and sequence of each task.
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
IX] REFERENCES:-
Process Product
Total(25)
Related(7.5) Related(17.5)
PRATICAL -3
Gather Application Specific requirements for assimilate into RE model. The functional requirement is
organized in two section; Requirement of your project and requirement of your personal computer.
1. Functional Requirement: It covers the main function that should be provided by the system. When
expressed as user requirements they are usually described on an abstract way. However, more
specific functional system requirements describe the system functions, its input, processing, how
it’s going to react to a particular input, what the excepted output.
2. Nonfunctional requirement: These are the constrains on the function provided by the system. The
constraint like, how many process the system can handle what are the security issues the system
needs to take care of such as SQL injections. The hate of failure what are the languages and tools
will be used, what are the rules you need to follow the ensure the system.
IX] CONCLUSION:
…THUS,WE HAVE TO PERFROMED PRACTICAL SUCCESSFULLY.
X] EXERCISE:
1. Gather and write application specific requirement for your any micro project.
ANS -1. Requirements Elicitation: getting business requirements from relevant stakeholders to understand
user need.
2.Requirements documentation: Codifying that information in the form of user stories and features
specifications so they are accessible to the project team.
3.Requirement Understanding: making sure everyone’s on the same page about what the heck you are all
trying.
4. Establish project goals and objectives early.
ANS : Perhaps the most difficult most ever prone and most communication intensive software
development it can be successful only through an effective customer developer partnership requirement
elicitation methods
• Interviews
• Brainstorming sessions
• Facilitated application specification technique
• Quality function development
• Use case approach.
………………………………………………………………………………………………………
…………………………………………………………………………………………
XI] REFERENCES:-
5) http://www.google.com
6) http://softwarebaba.com
7) Software Engineering by press man
Process Product
Total(25)
Related(7.5) Related(17.5)
PRATICAL -4
Prepare broad SRS (Software requirement Software) for the above selected projects
I] PRATICAL SIGNIFICANCE
Prepare broad SRS (Software requirement Software) for the above selected projects
Prepared broad software requirement specification for the above defined project.
• PURPOSE:
The main purpose of this microproject is to maintain easy circulation system using computers and to
be provide different reports.
• SCOPE OF PROJECT:
The document only over the requirements specification for the library management system.
• SECURITY REQUIREMENT:
The user should be simple and easy to understand and use also be an interactive interface
software provides good graphical interfaces for the user and administrator can operate
on the system.
• RELIABILITY:
The system shall be recovered within 10 minutes if it is down the system must be able to extend to
store and deliver new content media types.
• EXTENSIBILITY:
System must be able to extend to support synchronization of content media based on share work item
structure system must be able to extend support data sharing between records.
VI] RESOURCES REQUIRED:-
VII] CONCLUSION:
THUS,WE HAVE TO UNDERSTAND SRS AND PERFORMED PRACTICAL SUCCESSFULLY.
VIII] REFERENCES:-
a. http://www.google.com
b. http://softwarebaba.com
c. Software Engineering by press man
Marks
Sign of Teacher
obtained
Process Product
Total(25)
Related(7.5) Related(17.5)
PRATICAL -5
Prepare USE Cases and Draw Use Case Diagram using modelling Tool
I] PRATICAL SIGNIFICANCE
A use case diagram software and system engineering term that describe how a user uses a system to accomplish
particular goal. A use case act as a software modeling technique that defines the features to be implemented
and the resolution of any errors that may be encountered.
To prepare use case and draw use case diagram using software modelling tool.
• Actor:
The user that interact with the system and system an actor can be a person an organization
or an outside system that interact with your application
• Use case:
The use case describe what the system does and how the actor use it but not how the system operates
internally
………………………………………………………………………………………………
• Relationship:
A relationship is a connection between model elements. A relationship is a type of model elements
that adds semantics to a model by defining the structure and behaviour between the model elements.
………………………………………………………………………………………………
VII] CONCLUSION:
…THUS WE HAVE UNDERSTOOD USE CASE AND DRAW USE CASE DAIGEAM
SUCESSFULLY.………………………………………………………………………………
VIII] REFERENCES:-
d. http://www.google.com
e. http://softwarebaba.com
f. Software Engineering by press man
ANS:…1.PRIMARY ACTOR- people who use the main system functions are referred as
primary.
2.SECONDARY ACTOR- people who perform administrative or maintenance tasks are referred
as secondary
3.EXTERNAL ACTOR- the hardware devices which are required as part of application domain
and must be used are referred an external.
4.OTHER SYSTEM ACTOR- the other system with the system must interact referred as other
system actor.
PRATICAL -6
Develop the activity diagram to represent flow from one activity to another for software development
I] PRATICAL SIGNIFICANCE
Develop the activity diagram to represent flow from one activity to another for software development
…3…………………………diamond…shape…represent…decision.…………………………………………
…………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
…4…………………………arrow represents as a connector
…………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
…5………………………………………………………………………………………………………double
circle represents end of the activity ………………………………………………………………………
………………………………………………………………………………………………………
VII] CONCLUSION:
…THUS WE HAVE UNDERSTOOD ACTIVITY DIAGRAM FOR WEB BASED SOCIAL NETWORK
VIII] REFERENCES:-
• http://www.google.com
• http://softwarebaba.com
• Software Engineering by press man
USER ID/PASSWORD
LOGIN
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
SEARCH MESSAGE
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
REQUEST SEND
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
YES/NO
………………………………………………………………………………………
………………………………………………………………………………………
Process Product
Total(25)
Related(7.5) Related(17.5)
L
PRATICAL -7
I] PRATICAL SIGNIFICANCE
There are several notation as well as languages exists for the purpose of representation software
design. Some of them help to describe a structural organization, some are used to represent
behaviour yeah of system.
We develop data Designs using DFD Decision Table & ER diagram IV]
0 DFD: …
the system as single process with its relationship to external entities .represent the
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
entire system as say single bubble with input and output data indicated by incoming
outgoing arrows.
…………………………………………………………………………………………
…………
………………………………………
……………………………………………………………… ……………………………..
Level 1 DFD:
In first level DFD the context diagram is decomposed into multiple bubbles processes in this level
we highlight the main function of the system and breakdown the high level process of zero level
DFD subprocess.
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
……………………………………………
Level 2 DFD
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
In 2 level DFD goes one step deeper into part of one level DFD. It can be used to plan or record
the specific necessary detail about the system functioning
………………………………………………………………………………………………………
……………………………………
…………………………………………………………………
ER Diagram:
Er diagram stand from entity relationship diagram also known as ERD diagram that displays the
relation of entity set store in a database. In other word er diagram help to explain the logical
structure of database er diagrams are created based on 3 basic concept entities ,attributes and
relationship. Er diagrams contain different symbols that use rectangle to represent entities ovals
to define attributes and diamond shape to represent relationship.
………………………………………………………………………………………………………
Decision Table :
A decision table is a schedule rule logic entry in table format that consist of condition
represented in the row and column headings and actions represent as the intersection points of
the conditional cases in the table decision tables are best suited for business rules that have
multiple conditions.
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………