Professional Documents
Culture Documents
Swikar - Acharya - LC00017000872 - System Analysis and Design.
Swikar - Acharya - LC00017000872 - System Analysis and Design.
)/ Second semester
LCID: ILC00017000872
Assignment No: 1
Date: I15-07-2020
Swikar Acharya 1
BIT 123 System Analysis and Design BIT(Hons.)/ Second semester
Swikar Acharya 2
BIT 123 System Analysis and Design BIT(Hons.)/ Second semester
Swikar Acharya 3
BIT 123 System Analysis and Design BIT(Hons.)/ Second semester
Swikar Acharya 4
BIT 123 System Analysis and Design BIT(Hons.)/ Second semester
Swikar Acharya 5
BIT 123 System Analysis and Design BIT(Hons.)/ Second semester
Answers:
Systems analysts often analyze how customers communicate with innovation and how
organizations work by analyzing the input and preparation of information and the
generation of data in order to improve organizational forms. Most changes integrate
extended back for laboratory activities and consumer trading forms by using
computerized data structures. The description illustrates a descriptive, expository
method for evaluating and potentially making progress and what is happening within
the particular setting faced by consumers and generated by a company. Our definition
of a research context has to be precise. The investigator must be able to deal with
individuals in all portrayals and have computer expertise. The auditor plays different
roles, sometimes juggling several at once. The three basic positions of the systems
analyst are a expert, professional advocate and shift operator.
i Communication Skills: System analyst should have the ability to fluent and speak
and flair of working with all levels of managerial positions of the organization.
Teaching & selling ideas: System analysts should have the ability to educate other
people on the use of computer systems and the sale of ideas and the promotion of
innovations in computer problem solving.
Swikar Acharya 6
BIT 123 System Analysis and Design BIT(Hons.)/ Second semester
Analysis: A summary of the new System. Faults are found. This can be achieved by
speaking with support staff and interviewing app users.
Plan and requirements: Specifications are set for new program. Concrete reform plans
in particular need to address the shortcomings in the current program. Other listed factors
include critical features, capabilities and functions.
Design: The framework is planned which it proposes. Plans are laid out for physical
design, infrastructure, operating systems, programming, communication, and security
issues.
Development: The new program is under development. We need to get the latest
modules and applications, and update them. Device users must be educated on how to use
it.
Swikar Acharya 7
BIT 123 System Analysis and Design BIT(Hons.)/ Second semester
Testing: All measurements of the performance must be checked. Changes have to be
made at this stage, where possible. Tests performed by quality assurance teams (QA) may
require systems integration and system testing.
Deployment: The device is part of a system of development. This can be done in various
ways. The new system may be phased in and the old system gradually replaced, depending
on the program or location. In other cases it may be more cost-effective to shut down the
old system and implement the new system in one go.
Upkeep and maintenance: This phase involves software change and update once it is in
service. To best consistently suit the end-user needs, hardware or software can need to be
modified, replaced, or changed in any way. Users of devices will be kept up to date on new
updates and procedures.
Swikar Acharya 8
BIT 123 System Analysis and Design BIT(Hons.)/ Second semester
Prototype Model:
The concept model is not a complete design by itself. The concept model also has
plenty of detail not designed into it. The basic purpose of the prototype model is to have a
structure that gives functionality overall. It is a slow-processing technique. This reduces
costs. It is a complex framework and beyond the initial plans, program scope is increasing.
Agile Model:
Agile is used for quick planning, fast development, rapid release and rapid revision. The
Agile method is polyvalent. When the project manager isn't experienced, it can turn into a
big sprint sequence and come in late and over-budgeting. Agile is very flexible.
Prototype and Agile both require gradual changes over multiple periods but they are not
exactly the same. The concept involves repeating at the planning level and arranging to
shape simple choices that are used to guide progress. The model is removed from the
object, and the designers start coding the product once again. The iterative handle in Agile
is in the middle of the advance stage. A Minimum Viable Product (MVP) is made and has
been attempted and pursued over several cycles after that. The MVP is essentially like a
model itself, but it is not disposed of and is continually updated instep until it is the ultimate
object. Agile centers on computer program improvement, whereas fast prototyping focuses
on plan practices. The prototype can be utilized nearby an agile methodology when it is
important to get input sometime recently the advancement of the MVP starts, but this is
often situation-dependent and not common practice.
Swikar Acharya 9
BIT 123 System Analysis and Design BIT(Hons.)/ Second semester
7. Make a comparison chart for waterfall vs spiral model.
Answer:
Waterfall model:
Spiral Model:
Given the spiral model capabilities in advancement planning. Within a spiral model
errors or hazards are detected and updated prior to this. Despite the fact the designers are
focusing on winding architecture. While showing that Winding is being used for a major
extension. Given the fact that determinations are needed within the winding display and
early arrangement. Changing the versatility of the spiral model isn't alarming. There is a
small danger inside the number within the winding illustrate. Given the fact that the
fetched spiral model is outstandingly small.
Swikar Acharya 10
BIT 123 System Analysis and Design BIT(Hons.)/ Second semester
Answer:
Rapid Application Development (RAD):
RAD is a set of tools and techniques that can be paired with traditional methods to construct
an application faster than normal. This does not substitute SDLC but complements this,
because it is more based on process definition and can be paired well with the object-
oriented approach. Its job is to create the application by quickly and incrementally
implementing the user requirements specification through tools such as visual basic, power
builder etc.
The phases in RAD are:
1. Business modeling
2. Data modeling
3. Process modeling
4. Application generation
5. Testing and turnover
Advantages of RAD model:
1. Reduced development time.
2. Quick initial reviews occur
3. Increase reusability of components
4. Encourage customer feedback
5. Integration from very beginning solves a lot of integration issues.
Disadvantages of RAD model:
1. Depends on strong team and individual performances for identifying business
requirements.
2. Only system that can be modularized can be built using RAD.
3. Requires highly skilled developers/designers.
4. High dependency on modeling skills.
5. Inapplicable to cheaper projects as cost of modeling and automated code
generation is very high.
Swikar Acharya 11
BIT 123 System Analysis and Design BIT(Hons.)/ Second semester
JAD Advantages:
• By replacing months of conventional interviews and follow-up meetings it saves
time and costs.
• Organizational culture that promotes collaborative problem-solving is useful.
• Fosters structured relationships between employees of different levels.
• It can creatively contribute to design growth.
Swikar Acharya 12
BIT 123 System Analysis and Design BIT(Hons.)/ Second semester
• Allows fast growth and increases information system ownership.
JAD Disadvantages:
Different opinions within the team make it difficult to align goals and maintain
focus.
Depending on the size of the project, JAD may require a significant time
commitment.
Swikar Acharya 13