ASSIGNMENT- 1

ON

SYSTEM ANALYSIS AND

DESIGN
 SESSION: 2019-22

SUBMITTED TO: SUBMITTED BY :

ANKUR GUPTA KUNAL
A.P IN CSE DEPTT. BBA 6th SEM
VCE, Rohtak R.NO. 19/BBA/16

VAISH COLLEGE OF ENGINEERING,ROHTAK

QUES-1 EXPLAIN:-

(a) Feasibility Study

A feasibility study is an analysis that considers all of a
project's relevant factors—including economic, technical, legal, and
scheduling considerations—to ascertain the likelihood of completing
the project successfully.
However, a feasibility study isn't only used for projects
looking to measure and forecast financial gains. 

b) Cohesion
Cohesion is the measure of closeness of the relationship
between its components. It defines the amount of dependency of
the components of a module on one another. In practice, this means
the systems designer must ensure that − They do not split essential
processes into fragmented modules.

c) System Analyst
A systems analyst is a person who uses analysis and
design techniques to solve business problems using information
technology. Systems analysts may serve as change agents who
identify the organizational improvements needed, design systems to
implement those changes, and train and motivate others to use the
systems.
Systems analysts assess the suitability of information systems in
terms of their intended outcomes and liaise with end users, software
vendors and programmers in order to achieve these outcomes.
 d) Coupling
Coupling is the degree of interdependence between
software modules; a measure of how closely connected two routines
or modules are the strength of the relationships between modules.
Coupling is usually contrasted with cohesion. Low coupling often
correlates with high cohesion, and vice versa. Low coupling is often
thought to be a sign of a well-structured computer system and a
good design, and when combined with high cohesion, supports the
general goals of high readability and maintainability.

e) Questionnaire
A questionnaire is a research instrument that consists
of a set of questions or other types of prompts that aims to collect
information from a respondent. A research questionnaire is typically
a mix of close-ended questions and open-ended questions.
The data collected from a data collection questionnaire can be both
qualitative as well as quantitative in nature. A questionnaire may or
may not be delivered in the form of a survey, but a survey always
consists of a questionnaire.
Ques: 2 Explain system development life
cycles (SDLC)? Explain the steps involved in
system development life cycle?

The systems development life cycle (SDLC) is a conceptual model

used in project management that describes the stages involved in an
information system development project, from an initial feasibility
study through maintenance of the completed application. SDLC can
apply to technical and non-technical systems. In most use cases, a
system is an IT technology such as hardware and software. Project
and program managers typically take part in SDLC, along with system
and software engineers, development teams and end-users.
Every hardware or software system will go through a development
process which can be thought as an iterative process with multiple
steps. SDLC is used to give a rigid structure and framework to define
the phases and steps involved in the development of a system.
Steps in SDLC
SDLC can be made up of multiple steps. There is no concrete set
number of steps involved. Around seven or eight steps appear
commonly; however, there can be anywhere from five upwards to
twelve. Typically, the more steps defined in an SDLC model, the more
granular the stages are.
In general, an SDLC methodology follows these following steps:
1. Analysis: The existing system is evaluated. Deficiencies are
identified. This can be done by interviewing users of the system
and consulting with support personnel.
2. Plan and requirements: The new system requirements are
defined. In particular, the deficiencies in the existing system
must be addressed with specific proposals for improvement.
Other factors defined include needed features, functions and
capabilities.
 3. Design: The proposed system is designed. Plans are laid out
concerning the physical construction, hardware, operating
systems, programming, communications and security issues.
4. Development: The new system is developed. The new
components and programs must be obtained and installed.
Users of the system must be trained in its use.
5. Testing: All aspects of performance must be tested. If
necessary, adjustments must be made at this stage. Tests
performed by quality assurance (QA) teams may include
systems integration and system testing.
6. Deployment: The system is incorporated in a production
environment. This can be done in various ways. The new
system can be phased in, according to application or location,
and the old system gradually replaced. In some cases, it may be
more cost-effective to shut down the old system and
implement the new system all at once.
7. Upkeep and maintenance: This step involves changing and
updating the system once it is in place. Hardware or software
may need to be upgraded, replaced or changed in some way to
better fit the needs of the end-users continuously. Users of the
system should be kept up-to-date concerning the latest
modifications and procedures.
Other steps which may appear include project initiation, functional
specifications, detailed specifications, evaluation, end-of-life and
other steps that can be created by splitting previous steps apart
further.
Ques: 3 Construct Data Flow Diagrams
(DFDs)? Explain through a suitable example.

A data flow diagram (DFD) maps out the flow of information for any
process or system. It uses defined symbols like rectangles, circles and
arrows, plus short text labels, to show data inputs, outputs, storage
points and the routes between each destination. Data flowcharts can
range from simple, even hand-drawn process overviews, to in-depth,
multi-level DFDs that dig progressively deeper into how the data is
handled. They can be used to analyze an existing system or model a
new one. Like all the best diagrams and charts, a DFD can often
visually “say” things that would be hard to explain in words, and they
work for both technical and nontechnical audiences, from developer
to CEO. That’s why DFDs remain so popular after all these years.
DFD rules and tips
 Each process should have at least one input and an output.
 Each data store should have at least one data flow in and one
data flow out.
 Data stored in a system must go through a process.
 All processes in a DFD go to another process or a data store.

The Level-0 DFD, also called context diagram of the result

management system. As the bubbles are decomposed into less and
less abstract bubbles, the corresponding data flow may also be
needed to be decomposed.

Example:-