0% found this document useful (0 votes)
107 views

System Analysis and Design MOCK

Prototyping is a useful technique for gathering user requirements but should not replace the systems development life cycle (SDLC). While prototyping allows for early user feedback, it does not encompass all phases of the SDLC like planning, analysis, design, implementation, and maintenance. Prototyping is best used as part of the SDLC rather than as a replacement for the full methodology.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
107 views

System Analysis and Design MOCK

Prototyping is a useful technique for gathering user requirements but should not replace the systems development life cycle (SDLC). While prototyping allows for early user feedback, it does not encompass all phases of the SDLC like planning, analysis, design, implementation, and maintenance. Prototyping is best used as part of the SDLC rather than as a replacement for the full methodology.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

QUESTION 1

1. Prototyping of information systems is a worthwhile technique used


for quickly gathering specific information about users’ information
requirements. However, some experts argue that prototyping
should be considered as an alternative to the systems
development life cycle. Discuss this assertion.

Prototyping is a helpful procedure for rapidly assembling explicit data


about clients' data prerequisites, and it very well may be an important
piece of the frameworks improvement life cycle (SDLC).

Prototyping, according to some experts, should be considered an


alternative to the SDLC.

Planning, analysis, design, implementation, and maintenance are all


parts of the SDLC, which is a method for building information
systems. The goal of the SDLC is to create a high-quality information
system that meets the needs of users. Each step builds on the
previous one.
On the other hand, prototyping is a method that involves creating a
preliminary version of a system to get feedback and improve the
design. A prototype can be used to evaluate user interfaces, test
various design options, and get feedback on system functionality.
While prototyping can be a useful component of the SDLC, it should
not take its place.
The fact that prototyping does not cover all the steps in the SDLC is
one of the main reasons why it should not be used in place of the
SDLC.
The fact that prototyping can be time-consuming and costly is yet
another reason why it should not be considered an alternative to the
SDLC. Prototyping can be a cost-effective method for gathering
feedback and improving system design.
In conclusion, although prototyping is a useful method for getting
feedback and improving system design, it should not be used in place
of the SDLC
While prototyping can be a useful component of the SDLC, it should
not take its place.

QUESTION 3

1. Explain the concept of joint application design and discuss any


four situations that warrant the use of it in place of personal
organizational interviews

ANSWER

Joint Application Design (JAD) is a structured method for designing and


developing an information system together with users, stakeholders, and
developers. JAD's objective is to guarantee that the final system is
compatible with the organization's objectives and meets the
requirements of stakeholders and users.

JAD maybe in more effective and efficient in the following instances:

1. Systemic issues: To ensure that all requirements are identified


and addressed, JAD can provide a structured and collaborative
method for gathering input from all stakeholders. Personal
organizational interviews may not be sufficient to gather all
necessary information when the system being developed is
complex and involves numerous stakeholders.

2. Limitations on time: Personal organisational interviews can take


a long time, because it involves all stakeholders working
together. JAD can be more of an effective method of
information collection.

3. Resolving disputes: At the point when there are clashing


assessments among partners, individual hierarchical meetings
may not be able to settle these matters. But with JAD,
stakeholders can collaborate to identify and resolve these
conflicts.

4. High user engagement: Personal organisational interviews may


not be adequate to ensure that users’ feedback is fully
incorporated into the system design when user involvement is
essential to the system’s success. JAD involves stakeholders
and users in the design process to guarantee that the final
system meets their requirements.

QUESTION 4.
The head of computer science department of Ho Technical University
has conceived an idea to build a tutorial system to be used by
students in the department. The tutorial system will enable students
to search for lecturers within the University and book appointment
with them directly. Students will be able to use their student ID and
password to login to the system and book appointments with a
lecturer of their choice based on the search criteria. The secretary of
the department will be responsible for maintaining the courses,
lectures, and appointments within the system. The secretary will also
use the system to generate reports to prepare payrolls for the
lecturers who attend their reserved appointments. As a young
systems analyst who has been hired by the department, you are
required to draw a use case diagram for this tutorial system.

Answer

1.
Use Cases:

1. Search for Lecturer


2. Book Appointment
3. View Appointments
4. Maintain Courses
5. Generate Reports

The use cases identified in the system are:


1. Search for Lecturer: This use case allows the student to
search for a lecturer based on specific criteria such as course or
lecturer name.
2. Book Appointment: This use case allows the student to book
an appointment with a lecturer of their choice based on the search
criteria.
3. View Appointments: This use case allows the student to view
their appointments that they have already booked with a lecturer.
4. Maintain Courses: This use case allows the secretary of the
department to maintain the courses, lectures, and appointments
within the system.
5. Generate Reports: This use case allows the secretary of the
department to generate reports to prepare payrolls for the lecturers
who attend their reserved appointments.
Overall, this use case diagram provides a high-level overview of
the tutorial system, its functionalities, and the interactions between
actors and the system.

QUESTION 6
Discuss the seven phases of the systems development life cycle.

Answer

Information systems are designed, developed, and maintained


using the structured approach known as the Systems
Development Life Cycle (SDLC). Among these phases are:
1. Planning: The objectives of the system, the scope of the
project, the resources required, and the creation of a project plan
are all part of this phase. The project team collaborates with
stakeholders during this phase to establish project timelines and
identify constraints and requirements.
2. Analysis: The project team examines the current system in
depth during this phase to identify its strengths and weaknesses.
They also gather information from stakeholders like users and
management to determine the new system's requirements. The
group then fosters a framework plan that meets the recognized
necessities.
3. Design: During this stage, the framework configuration is
created, including the specialized details, information stream
outlines, and UI plan. Additionally, the system's hardware and
software are selected by the project team.
4. Development: The actual development of the system takes
place during this phase. Database development, unit and system
testing, and code writing are all performed by the group. After that,
the system is tested and integrated.
5. Testing: The project team conducts extensive testing during
this phase to guarantee that the system works as intended.
Functional testing, performance testing, and security testing are all
types of testing.

You might also like