Scribd
Upload
81 views

CSC 1017 System Analysis and Design First Assignment

This document contains an assignment submission for a System Analysis and Design course. The submission includes the student's name, ID number, course details, and date of submission. It addresses several questions related to system development methodologies, prototyping, requirements gathering, and key concepts in systems analysis.

Uploaded by

Achyut Neupane
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
81 views

CSC 1017 System Analysis and Design First Assignment

This document contains an assignment submission for a System Analysis and Design course. The submission includes the student's name, ID number, course details, and date of submission. It addresses several questions related to system development methodologies, prototyping, requirements gathering, and key concepts in systems analysis.

Uploaded by

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

Programme Name: BCS

Course Code: CSC 1017

Course Name: System Analysis and Design

Assignment: First Assignment

Date of Submission: 29 June 2022

Submitted By: Submitted To:

Student Name: Achyut Neupane Faculty Name: Navraj Khanal

IUKL ID: 042103900002 Department: PO

Semester: 1st Semester

Intake: September 2021


Q System development methodology refers to the framework that is used to structure, plan, and
control the process of developing an information system.
A Software development methodologies think about the whole process of making software, from
the idea to the final release. There are several components that contribute to software
development, but developers all focus on a small part of the process: programming. Software
development techniques may be highly helpful when utilized in moderation, but they must be
used as a radar to helping detect potential issues.

a) Explain ONE (1) type of methodology called Prototyping.


→ The software development model for prototyping is to build, test, and make changes
to the prototype in iterative manner. A prototype is the first version of a system that
is used to show ideas and try out different design choices.
→ A prototype could be a "throw-away" that is just a "quick and dirty" attempt to make
something that looks like the finished product but isn't good enough for it.

b) List FOUR (4) Strength and Weakness of Prototyping methodology.


→ Strength
(a) Useful when user requirements are not clear or has any issues.
(b) Prototyping will be a plus point if the software design is complex and require
concrete evaluation.
(c) Protype are easy and quick to build than the final product for
approval/evaluation.
(d) Building prototype before final product will reduce development effort and
improve maintainability.
→ Weakness
(a) Prototyping will be difficult for adapting by general user.
(b) If a developer spends too much time making a prototype that is too complicated,
the project will take longer and cost more.
(c) Prototyping is prone to frequent changing in requirements. This will lead to less-
managed documentation.
(d) After seeing an early prototype, customers sometimes want the real product right
away.
c) State FOUR (4) reasons why do we need to adopt a methodology in system
development.
→ The four reasons why adopting methodology in system development is important:
(a) Adopting to any specific methodology leads to a better quality in the system
developed.
(b) One person might work on a project and then be replaced by someone else. For
the new person to know what the first person did and pick up where they left off,
system development methodologies are very important. It saves time and makes
the team more productive.
(c) Software development methodologies are beneficial in that they manage the
execution of the project and lower the expenses of development.
(d) One of the most important things in an organization is communication. Adopting
any methodologies can help people involved in the system communicate with
each other.
Q Describe FIVE (5) characteristics that a good system analyst should have during requirement
determination.
A To analyze a system effectively, a Systems Analyst must first establish its requirements, as well as
its goals and objectives. In order to determine the requirements, a person has to be curious, which
demonstrates the importance of maintaining the stated characteristic while working as a Systems
Analyst.
During the process of determining requirements, a good system analyst need to show the
following characteristics:
a) The system analyst is expected to be able to communicate well both verbally and in
writing.
b) The analyst has to be able to get along well with others.
c) The analyst has to have strong listening skills and the ability to respond appropriately to
what other people say.
d) The analyst has to have a strong understanding of technology. The analyst is not required
to have a deep understanding of programming, but it is vital for them to have a basic
insight of concepts and terms.
e) The analyst has to have a strong understanding of business. Although it is not expected of
the analyst to be an expert in business, a good awareness of the environment in which
the customer operates is necessary.
Q Describe briefly:
a) Technical Feasibility
→ The process of determining whether or not a proposed system can be built by the
development organization is known as the technical feasibility assessment.
→ As part of this analysis, analyst should evaluate the development team's knowledge
and understanding of the potential hardware, software, and operating environments
that will be utilized. Analyst should also consider the size and complexity of the
system, as well as the team's prior experience working with systems that are
comparable.

b) Rapid Application Development


→ The term "Rapid Application Development" (RAD) refers to a specific process for the
creation of software or hardware systems that prioritizes rapid prototyping
above planning. The process of "planning" software that will be built using RAD occurs
concurrently with the actual development of the system.
→ By subdividing a larger project into a number of smaller ones, Rapid Application
Development seeks to achieve its primary goal of achieving rapid development of
high-quality systems at relatively low investment costs.

c) Structured Walkthrough
→ A method of static testing that is conducted in an organized way amongst a group of
peers in order to evaluate and analyze the technical components of the software
development process is called a structured walkthrough. The primary purpose of a
structured walkthrough is to identify issues with the product in order to make
improvements to its overall quality.
→ In most cases, technical discussion and the discussion of possible solutions to issues
identified during structured walkthroughs are NOT performed. It has been stated that
the purpose is not to fix issues but rather to identify issues. After the walkthrough has
been completed, it is the author of the output who is responsible for resolving any
problems that have been found.
d) System Analyst
→ Systems Analysts utilize analysis and design to address business challenges using
Information Technology. System analyst studies, designs, develops, implements,
supports, or manages computer-based information systems, including software
applications and computer hardware, to transform, store, protect, process, transmit,
and retrieve information.
→ Systems Analysts must understand a company's objectives and strategy and define its
information needs.

e) Joint Application Development


→ Joint Application Development, often known as JAD, is a prototype life cycle
methodology that brings together important users, managers, and systems analysts.
This methodology is quite similar to that of a group interview.
→ The goal of the Joint Application Development (JAD) is to concurrently gather system
requirements from important stakeholders. It is standard practice to stick to a
predefined sequence of responsibilities and agenda, and analysts direct the order in
which users engage to topics.

You might also like