You are on page 1of 8

Lovely Professional University

Department of CA

HOMEWORK-1

Homework Title/No: 1
Course Code: CAP 314

Course Instructor: Lect.Mr.Ketan Sood Course Tutor (if


applicable): NA

Date of Allotment: 15/02/2010 Date of submission:


26/02/2010

Student’s Roll Number: RE3902A05 Section No.:


E3902

Declaration:

I declare that this assignment is my individual work. I have not


copied from any other student’s work or from any other source except where due
acknowledgement is made explicitly in the text, nor has any part been written
for me by another person.

Student’s Sign:

Munish sharma

Evaluator’s Comments: ___________________________________________________

Marks obtained ____________ out of __________________


PART A

Q1. Take the example of student information system and introduce the
concept of software engineering in it.

Ans:- A student information system is a software application for


educational establishments to manage student data. Student information
systems provide
Student data and to receive data when ever needed. e . x for maintaining
the student record such as result of student, student fee record, and their
personal details such as their parentage, address, name ,an electronic
grade book, building student schedules, tracking student attendance, and
managing many other student-related data needs in a school, college or
university.

By introducing the concept of software engineering in student information


system it eases the work loads on the software developers and help them
to manage project effectively and efficiently.
While developing the student information system we
should follow the below steps to be considered for implementing it
effectively the example of a student information system is l.p.u. ums
system:-
a) First of all we have to check the feasibility of the project that is
student information system.

b) In the second step we have to Design the model of the student


information system. The design must contain the all modules or we
can say all parts of the student information system which we need
in that system.
c) When all the specifications are understood and design of the system
is ready the we move on to the next section in which we the system
is physically created. The required programs are coded, debugged
and documented.
d) After creation of software, the testing is done. The system should be
tested with some test data to ensure its accuracy and reliability. If
the software clears the test phase, then the next phase is
implemented.
e) The testing can be black box testing white box testing.

f) After the testing phase is over the created software is implemented


on the site or we can say for the operation for which it is created the
software implementation phase involves a conversion process from
the use of a present system to the operation of a new or improved
application. Conversion methods can soften the impact of
introducing new technology into an organization.

g) After the implementation phase there comes the maintained phase


in which we maintain the software so that it can work with the
present demands of the software user. This phase usually comes
after a span of time when user knows about some new requirements
or when they want software to change because of their changed
working conditions.

If we follow all these steps properly then we will be able to manage the
student information system properly or we can say in an effective and
efficient way.

Q2. As a software developer identify the different processes required in


software development by taking the example of any project you are
working on.

Ans: - SOFTWARE DEVELOPER: -- A software developer is a person who analyses


the business situation for which software is to be developed.

Let us take an example of a library system


In the library system :-
1. The developer wills first all analyses the current working system by which the library is
managed and see what the possible changes if applied are can improve the performance of the
system

2. A developer watches how books are issued and what are the procedures for that he also
notice what happens when the time limit is over how the fine system is working.
Then he decides what are the other features that should be included in the system to make it
to work more effectively and efficiently.

3. Then the design is developed for the desired system.

4. After the design is ready the coding phase starts in which we code for the according to the
system design that we have developed. The coding done by the developer should be error free
so that it can solve the purpose for which it is to be developed.

5. The developer must document the system properly so that if after some time when
maintenance will be done then it should be easily understood by a new developer.

6. After these all phases are over the newly coded system is tested with the user given values
to know whether it is functioning properly or not.
At last the newly developed system is handed over to the user for working.
Q3. How will you implement software process model in your software?
Write down the steps f or the same.

Ans:- A software process model starts with the conceptualisation of the software product
and ends when the functioning of the product is over the software life cycle model represents
a descriptive and diagrammatic model of a software product with a series of identifiable
phases through which the software product passes during its lifetime.
Examples :-
• Classical waterfall model
• Iterative waterfall model
• Prototyping model
• Evolutionary model
• Spiral model
• Rapid application development model
• Incremental model
• V model

Let us take the example of the waterfall model and see the various phases through which it
passes.
The steps of the Waterfall Model are as follows: -

a. Feasibility Study
b. Requirements Analysis and Specification
c. Design
d. Coding and Unit Testing
e. Integration and System Testing
f. Maintenance

a) Feasibility Study:- The aim of feasibility study is to determine whether the demands
desired by the user are feasible or not the feasibility so a software is checked out on
three basis:-
Operational, technical and financial.
If a project passes these criteria of feasibility then it is considered otherwise the plan
is left or other options are checked.

b) Requirement Analysis and Specification: - Its aim is to understand the exact


requirements of the customer and to document them properly. This phase consists of
two activities: -
(a) Requirement gathering and Analysis
(b) Requirement Specification
The goal of requirements gathering activity is to collect all
relevant information from the customer regarding the product to be developed.
c) Design:- The goal of design phase is to transform the requirements specified in the
SRS document into a structure that is suitable for implementation in some
programming language.
d) Coding, Unit Testing and Component Testing:- The purpose of coding and unit
testing phase of software development is to translate the software design into source
code. Each component of the design is implemented as a program module. The unit
testing is that in which each module is executed and tested. The component testing
evaluates the combined software parts.

e) Integration and System Testing: - Integration of modules is done once they have
been coded and unit tested. During this phase, the modules are integrated in a planner
manner. During each integration step, the partially integrated system is tested and a
set of previously planned modules are added to it.

f) Maintenance: - Maintenance of software requires much more than the effort


necessary to develop the product itself. It mainly involves two activities: -
(a) Correcting errors that were not discovered during the product development phase.
This is called corrective maintenance.
(b) Improving the implementation of the system and enhancing the functionalities of
the system according to the customer’s requirements. This is called perfective
maintenance.

After all these processes the life cycle of the is over and our software is ready.

PART B

Q4. Create SRS document for any software project.

Ans:- when the software is to be developed is the simple one and not the complex one the
SRS development stage follows after the requirement analysis stage.
However for developing the large system the SRS is developed side by side with the process
of requirement analysis.
SRS help the software developer to develop the software with the minimum errors the system
analyst develops the SRS which consist of the following inherent features
Correctness,completeness,clarity,verifiability,understandability,consistency,modifiability,trac
eability,ranking according to importance or stability .

The important parts of SRS are:-


1. Functional Requirements
2. Non-functional Requirements
3. Goals of Implementation

Functional Requirements discusses the functionalities required from the system.


Non-Functional Requirements include the characteristics of the system that cannot be
expressed as a function such as maintainability of the system, portability of the system,
usability of the system etc.

Goals of Implementation discuss some general suggestions regarding development. These


are the items which the developers might keep in their mind during development so that
development system may meet some aspects that are not required immediately.

SRS for an Inventory Control System


The inventory control system of any company includes
1. Purchasing
2. Manufacturing
3. Customer Orders

Interface with Purchasing:-

When an order from a vendor arrives, our Purchase Order Number on the vendor’s
invoice will be used to locate the PO and other related documents, such as vendor
proposals, price lists, product specifications.

Interface with Manufacturing:-

Manufacturing requests materials


Manufacturing wants to store finished goods
Interface with Customer Order Entry:-

Customer Order Entry wants to ship goods


Customer Order Entry wants to store returned goods

Diagram for an Inventory Control Document SRS:-

Custome
r order
entry

Inventor
y
Manufactur
Control ing
System
Purchasing

Objectives of Inventory Control System

Inventory Control Systems main objective is to keep track of all the parts and finished goods
in the warehouses and all the transactions involving these parts and goods.

An automatic purchase order generation when the stock levels of parts falls below the
minimum has been contemplated but postponed to a future date.

Functions of Inventory Control System the main functions of Inventory Control System are:-

1. Entering new parts into the inventory


2. Issuing parts to Manufacturing
3. Entering finished goods to the inventory
4. Providing Sales personnel with inventory information
5. Issuing goods to customers

Q5.Explain different document conventions you will use while writing SRS
for your project.

Ans:-
the information in SRS should be organised in to sections and subsections this standard
format of SRS allows the developer to check if all the requirements are specified in the SRS
and easily trace any missing requirements in the SRS .this standard format also makes the
SRS understandable IEEE provides a standard format for SRS the IEEE allow different
format for organising information in different projects the general framework of SRS is
Introduction
a) Purposes of document
b) scope of document
c) list of definitions, acronyms, abbreviations
d) references

2. Overview of the document:-

a) overall description of the software requirements


b) product perspective\
c) product function
d) end user characteristics
e) general constraints
f) assumptions and dependencies

3. Specific requirements

Q6.Implement the scenario of Object oriented modelling in your project.

Ans: - Object Oriented Modelling: - Object Oriented Modelling is mainly used in computer
programming. These techniques are used during the analysis, design and implementation of
the system. The Object-Oriented paradigm assists the programmer to address the complexity
of a problem domain by considering the problem not as a set of functions that can be
performed but primarily as a set of related, interacting Objects.

For example in a student information management system of a college a student is an


object .the student object has many attributes such as name of the student ,roll no,reg no
,address ,grades of the student ,attendance.

The object-oriented model is based on a collection of objects, like the E-R model.

• An object contains values stored in instance variables within the


object.
• Whether the record-oriented models, these values are themselves
objects.
• Thus objects contain objects to an arbitrarily deep level of nesting.
• An object also contains bodies of code that operate on the object.
• These bodies of code are called methods.
• Objects that contain the same types of values and the same methods are
grouped into classes.
• A class may be viewed as a type definition for objects.
• Analogy: the programming language concept of an abstract data type.
• The only way in which one object can access the data of another object
is by invoking the method of that other object.
• This is called sending a message to the object.
• Internal parts of the object, the instance variables and method code, are
not visible externally.
• Result is two levels of data abstraction.

You might also like