Scribd
Upload
10 views19 pages

Week 1

This document provides an overview of a 6-week software engineering laboratory course syllabus. Week 1 focuses on developing a problem statement. Weeks 2-4 cover preparing software requirements, implementing structural and behavioral modeling using case tools. Weeks 5-6 develop test cases for unit, integration, and various white and black box testing techniques. The document also provides information on the modeling tool StarUML, including its features and how to download and install it.

Uploaded by

thorarjun4
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
10 views19 pages

Week 1

This document provides an overview of a 6-week software engineering laboratory course syllabus. Week 1 focuses on developing a problem statement. Weeks 2-4 cover preparing software requirements, implementing structural and behavioral modeling using case tools. Weeks 5-6 develop test cases for unit, integration, and various white and black box testing techniques. The document also provides information on the modeling tool StarUML, including its features and how to download and install it.

Uploaded by

thorarjun4
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 19

Software Engineering Laboratory

Syllabus
Week-1: Development Of Problem Statement.
Week-2:Preparation Of Software Requirement Specification
Document
Week-3:Implementing Structural Modelling Design Phase Using
Case Tools.
Week- 4:Implementing Behavioural And Architectural Modelling
Design Phase Using Case Tools.
Week-5:Develop Test Cases For Unit Testing And Integration
Testing
Week-6:Develop Test Cases For Various White Box And Black
Box Testing Techniques.
Software : Star UML
Star UML is a UML (Unified Modeling Language) tool, introduce by
MKLab.

It is an open-source modeling tool that supports the UML framework


for system and software modeling.

StarUML is based on UML version 1.4, it provides 11 different types


of diagrams.
StarUML is actively supporting the MDA (Model Driven
Architecture).

It approaches by supporting the UML profile concept and


allowing it to generate code for multiple languages.

It also provides a number of bug fixes and improved


compatibility with the modern versions of the Windows
Operating System.

StarUML is mostly used by the Agile and small development


teams, professional persons and used by the educational institutes.
Features of StarUML
 It supports multi-platform such as macOS, Windows, and Linux.
 It involves UML 2.x.standard compliant.
 Includes Entity-Relationship diagram (ERD), Data-flow diagram (DFD), and
Flowchart diagram.
 It creates multiple windows.
 It has modern UX and dark and light themes.
 Featured with retina (High-DPI) display support.
 Includes model-driven development.
 It has open APIs.
 Supports various third-party extensions.
 Asynchronous model validation.
UML
The Unified Modeling Language (UML) is a general-purpose
modeling language.

The primary goal of UML is to define a standard way to


visualize how a system has been designed.

It is very similar to blueprints used in other areas of engineering.

UML is not a programming language, just a Visual Language.


Steps to Download and Install StarUML

Step 1: Go on the browser, and type in the URL https://staruml.io/


Step 2: Click on “Download for Windows”.

Step 3: Now, right-click on the downloaded file, select “Run as


Administrator” option.
Step 4: Installation gets start. After installation popup opens to ask
to buy a license. If you want to click on the “Buy Now” button or
else close that window. StarUML is ready to use.
WEEK-1
DEVELOPMENT OF PROBLEM
STATEMENT
Problem Statement
The problem statement is the initial starting point for a project.
The project agrees with what will be done at a high level.

The problem statement is intended for a broad audience and


should be written in non-technical terms.

It helps the non-technical and technical personnel communicate


by describing a problem.
Cont…
It doesn't describe the solution to the problem.

The input to requirement engineering is the problem statement


prepared by the customer.

It may give an overview of the existing system along with broad
expectations from the new system.
The first phase of requirements engineering begins with
requirements elicitation i.e. gathering of information about
requirements.

Here, requirements are identified with the help of customers and


existing system processes. So from here begins the preparation of
the problem statement.

A problem statement describes what needs to be done without


describing how.
EXAMPLE

To develop a PROBLEM STATEMENT


for a Library Management System.
Process Flow of Library Management System

A LMS lends books and magazines to members, who is registered in


the system.
Also, it handles the purchase of new titles for the LMS.
Popular titles are brought in multiple copies.
Old books and magazines are removed when they are out of date or
poor in condition.
The LMS can easily create, replace, and delete information about the
titles, members, and reservations from the system.
Online Resources :
Effective problem statements have these 5 components

https://www.betterup.com/blog/problem-statement#what-is-a-probl
em-statement
?

What is a Problem Statement? With Examples | Elsevier Blog


Task – 1 :
To Develop A Problem Statement For

1. ATM (Automatic teller machine)


2. Blood bank system
3. Railway reservation system

You might also like