MCSL 217
MCSL 217
MCSL 217
1.0 INTRODUCTION
Software Engineering relates to the process of development of quality software.
Normally, Software is the singlemost expensive item in a computer system. During
the life time of a system , about 95% of the cost is incurred on software and only 5%
on hardware. Computer AidedSoftware Engineering (CASE) tools help in many
software engineering tasks with thehelp of the information created using the
computer. CASE tools support software engineering tasks for the different phases of
Software Development Life Cycle (SDLC). MCS-0213 discusses various aspects of
Software Enginerring in detail. You must go through this course before taking the
practical in this lab. The lab sessions in this unit revolve around various phases of
software development.
This lab is an attempt to help you practice proper software development methodology.
You must do these software development activities (lab sessions) with the help of
suitable tools, preferably.
1.1 OBJECTIVES
After going through and working with the problems given in this section, you should
be able to:
1
The proposed software system should be able to: Software Engineering
Lab
read the structured data available in the Excel files and store it in a
Database system.
validate data of the database on the basis of predefined business rules.
prepare reports on data that is found to be in error during validation.
prepare MIS reports from the validated data.
……………………………………………………
4 RESOURCE REQUIREMENT
The Hardware, Software, and Tools are required for the three different environments,
viz., Development environment, Quality Control environment, and Deployment
environment. These resources may be documented accordingly.
2
Lab Manual 5 SCHEDULING
GANTT Chart
A very elementary Gantt or Timeline Chart for the development plan is givenbelow..
The plan explains the tasks versus the time they will take to complete.
PERT Chart
A suitable PERT Chart for the development plan can be given here.
6 BUDGETARY ESTIMATES
The whole budgetary estimates may be divided into resource procurement and
software development costs. The software development efforts and cost may be
estimated with the help of COCOMO or any other model used by the organization.
7 Summary
Please provide the summary here.
Cost Estimation
Creation of SRS
Traceability of requirements
Non-ambiguous requirements document
Creation of Models
Some of the partial samples for some of the above are illustrated here:
Development Plan, Economic Include the Gantt Chart, Pert Chart, Cost estimation, etc.
Feasibility and other feasibilities
INTRODUCTION
Background of the Project
The basic requirement of the user and working of the system are:
The Client should be able to upload the available data in Excel files into the
Database.
This data is then validated by the software called VALIDITY CHECKER. This
software contains the basic business rules and also produces error reports
…………………………………………….
Report Layout
Give the information about the layout of the report here.
TERMS OF REFERENCE
What is expected?
The expected system works by processing the employee data of an organization. The
data is to be stored securely in the database. Statistical operations are done on the data
to produce reports as desired by the client company.
Time Frame
The delivery deadline for the system is 6 months from the date of start of theproject.
What resources are available?
The resources that are available are.
Personnel (however , they need training)
Linux Operating System
Networked systems
Servers and Database Management System
EXISTING SYSTEM
Working of the Current System
You can write this topic only after doing the requirement analysis. Information from
the requirements gathering phase that includes outcomes of interviews of the
users, questionnaires filled by them and workflows that are currently functioning. In
the example , the current system
reads the data from Excel files and stores them into the database.
validates the data on the basis of business rules and generate reports to show
the errors in data.
enables for correction of data
creates MIS reports
Problems in the Current System
The problems of the current system are:
4
Lab Manual For every data collection cycle , new Excel-based system needs to bedeveloped
All the functions take a lot of time to complete.
……………………….
SYSTEM REQUIREMENTS
The following types of requirements can be freezed:
The system should be able to read the data from Excel files and store it inthe
Database.
………………….
PROPOSED SYSTEM
Project Outline
You may give the outline of the Proposed System here. Explain the terms anddata
references in the data dictionary.
DATA DICTIONARY
Some sample terms that are used in the documents :
Expansion of Additional
Name Where used
Name Description
In Functional
CLIENT
Diagrams and This is an Object
Class Diagrams
In Functional
Data Validation This is a Process
Diagrams
Specific Requirements
Interface Requirements
User Requirements
Hardware Requirements
Software Requirements
Logical Database Requirements
Basic Processing Actions of the System
Appendices
Input/Output Formats
Instruction for Security
Results of Fact Finding
Data Model
Functional Model
Process Specification.
INTRODUCTION
Purpose
SRS contains details of the proposed software system for the designers to design the
system . Thus, SRS is a means of communicating the findings of the analysis stage to
the design stage. The SRS includes .
Interface
Logical Database
Hardware
Performance and other constraints.
It also contains the assumptions made by the analyst and any systemic dependency.
Scope
The scope of SRS contains all the areas related to the project. The scope ofSRS
includes.
Proposed software description
Users of the proposed software
Functional requirements of the software
Assumptions and dependencies in the system
Constraints
Definition
.……………………..
Product and its
functions
………………………..
6
Lab Manual Benefits and Goals
………………………..
Overview
..………………………
OVERALL DESCRIPTION
Product Description
The Client should be able to upload the raw data in Excel files into the Database. The
raw data is then validated using ………
Product Functioning
The Raw data from the Clients is put into the database.
…………………………………………………..
Functions in the Project
There are five functions of the system.
User Verification
The User is asked to enters the Username and Password. The system checks the
validity of Username and Password, otherwise the User is asked to do so again. A
maximum of three valid attempts are given to the user.
Upload Raw Data
……………………….
Validate Data
……………………….
Put the Validated Data
……………………….
Generating Reports
…………………………..
Users of the Product
………………………
Assumptions
……………………
SPECIFIC REQUIREMENTS
Interface Requirements
The Interface requirements include.
Easy to follow Interface
Very less graphics
No hidden buttons
Relevant error messages
……………………………….
User Requirements
After a careful study of the requirements of the Client, analysts have come up with a
set of requirements.
…………………………………..
Hardware and Software Requirements
There are three environments that have been created for the project, viz.,
Development environment
Quality Control environment
Production environment
The hardware requirmemts for all the platforms may be indicated here.
7
Logical database Requirements Software Engineering
Lab
The following information is to be stored in the database:.
The Clients Raw data
The Clients Validated data
Username and Password.
APPENDICES
APPENDIX A
Login screen
The following screen that inputs the Username and Password from the User for
authentication of the User to the system is.
Login Id
Password
Close Login
APPENDIX B
INSTRUCTIONS FOR SECURITY
Security is an integral part of any system. Clients send their confidential data with
trust and it is our foremost duty to protect the security and privacy of the data of the
Clients.
………………………
APPENDIX C
RESULTS OF FACT FINDING
APPENDIX D
DATA MODEL
Classes involved in the Project
Clients
Excel Data Files
Reports
8
Software Engineering
Lab
PROCESS SPECIFICATION
Else, access is denied and the enter Username and Password screen isshown
again. This cycle will be done a maximum of three times
Flow Chart
START
Enter Username
and Password
Maximum 3 chances
Verify from
Database
Is Correct?
Print bad Username
and Password
No
Yes
STOP
11
Software Engineering
Lab
INTERFACE DESIGN
Login Screen
1.5 TESTING
…..
12
Lab Manual
TEST LOG
Function Purpose of Set of Test Case No of Test Number of
Test Cases per ID(s) Cases run Test Cases
Area Successful
Login The verificaiton of QT1-001 8 100%
username and
password
……
1.6 IMPLEMENTATION
It must contain the proper comments. The coding should be structured as per software
architecture.
VALIDATION CHECKS
Verification of the User
Both User Id and Password are mandatory
The size of User Id must be 10 characters long
COMMENTS
Comments are an integral part of any system. Like any properly developed and
maintained system with high quality, this system too has sufficient comments and
description of the processes, functions, classes, and data structures.
CODING STANDARDS
The defined coding standards of the software developers may be followed. A sample
clause in coding standard may be: “A consistent naming pattern is one of the most
important elements of predictability and discoverability in a managed code. For each
type, you must follow the defined capitalization styles, case sensitivity and word
choice.
1.8 SUMMARY
This section provides an introduction to software engineering lab in action. In this lab
section, we provide some basic information on how one can prepare the project plan,
Data dictionary, software requirement specification, Data model, functional model,
different kinds of design tools, data analysis, testing.You can find more details on
these topics in the MCS-213 : Software Engineering course. A learner should solve
the problems given in this section with the help of CASE/software tools to get the best
benefits from this section.
14