ICT103 System Analysis and Design Assignment Sample

Introduction

The motivation behind this report is to perform framework examination of the KOI library the board system. The lab needs to give a few improvements to existing systems. Therefore, the report incorporates the entire fringe, practical, as well as non-utilitarian business necessities that the procedure requires to actualize another process. This report likewise incorporates a business displaying movement graph for the new expansions of the KOI library the executive’s framework

Methodology

The Software Development Lifecycle (SDLC) is the procedure that product or different organizations use to create, oversee, plan, test, as well as actualize programming or frameworks. There are five primary strides to performing undertakings in SDLC: Or, SDLC is known as a framework. You can likewise utilize meanings of errands that must be performed to create predictable programming (Dehraj&Sharma, 2019).

SDLC Cycle

Source - (Dehraj & Sharma, 2019)

Steps in SDLC are defined below -:

1. Arranging: The initial phase in the product improvement lifecycle is planning. Because programming or frameworks must be successful, you should design before actualizing them

2. Plan: This procedure characterizes the framework design as well as form the framework dependent on explicit prerequisites.

3. Usage: This is a troublesome advance recorded as a hard copy code as well as introducing equipment as well as software. The execution may come up short because the procedure isn't constantly favourable.

4. Test: This causes you to realize that an issue has happened in the process. It likewise gives bit by bit directions to gaining from mistakes as well as adjusting them.

5. Documentation: Helps you comprehend programming that causes you to comprehend the reason as well as the motivation behind your framework or programming (Dehraj&Sharma, 2019).

SDLC Approach Types

The two types of SDLC approaches are described below.

Predictive approach

The prescient methodology gives a direct structure to creating explicit frameworks with explicit prerequisites as well as time-span particulars, just as pre-characterized forms.

Predictive Model Approach

Source - (Kaur & Kaur, 2015)

Advantages of a predictive approach

• Easy to design before you start

• Monitor as well as investigate the progress

• Developers are unmistakably mindful of what should be actualized

Disadvantages of the Predictive Approach

• It required some investment to guarantee that everything was done as expected, requiring regular checks, including arranging as well as observing investigation (Kaur&Kaur, 2015).

• If you have to make transforms, you should begin everything without any preparation.

Adaptive Approach

The process is very voluntary because it is not planned.

Adaptive Model Approach

Source - (Kneuper, 2017)

Advantages of an adaptive approach

• Consuming time is very less.

• Not much pre-planning is required

Disadvantages of an adaptive approach

• Difficult to predict (Kneuper, 2017)

• Won’t confirm the success rate of the system

SDLC Methodology

Among the various software methodologies, some are as follows -

1. Waterfall model

2. V-shaped model

3. Spiral models

4. Iterative model

5. Big Bang model

6. Agile model

Waterfall versus Agile Model

Waterfall Model

The waterfall model is one of the most seasoned as well as first models in the executed programming advancement lifecycle. Software improvement moves through direct structures, for example, cascades, as well as the following stage begins just when the past advance finishes.

Waterfall Model flow

Source - (Mohankumar & Anand Kumar, 2016)

Steps are very much dependent on each other.

Waterfalls Model benefit

1. Needs to define the requirements very clearly

2. Projects of short duration

3. Not follow the dynamic technology

4. Project definition is very clear

Waterfalls Model Disadvantages

1. Software will execute at the end

2. Uncertainty risk is very high

3. Not in favour of a change in requirements.

Agile Methodology

This isn't just a trial of the whole SDLC, yet a constant cycle exercise. This causes the group to react to the criticism the group got about the product. This dissects the item as well as improves the serious edge available.

Agile model flow

Source - (Mohankumar & Anand Kumar, 2016)

Agile method principle

1. Main goal is the development of software

2. Aware

3. Understandable methodology

4. User Friendly

Agile model advantages

1. Satisfaction of the customers

2. Less time in the updating of the software (Mohankumar & Anand Kumar, 2016)

3. Changes are possible

4. Reliable along with simple

Chosen Methodology

I pick an agile model for the given contextual analysis. The KOI Institute has numerous parts that require numerous procedures, so Agile is the ideal instrument for this study. Therefore, it is anything but difficult to part into subparts. And once in a while, the coordinated strategy requires basic upgrades or alterations.

Requirements

Below are the system requirements:

Functional Requirements of KOI Library Management System

This is a significant necessity, as well as is additionally a prerequisite for any framework, for example, moving outside a machine.

Some functional requirements are:

1. Approval: The suitable overseer must affirm the hardware before it tends to be held

2. To sort out everything appropriately, you should apply the suitable rules. Not just does everything assume a significant job, however, you need a decent clarification to be fulfilled

3. IT Equipment due date

4. Equipment Charges

Non-functional requirements of KOI Library Management System

They are not significant frameworks, as well as they are not significant without them. The framework will run regardless of whether there are no non-functional prerequisites.

The non-functional requirements are:

1. System Scalability

2. System Capacity

3. System Availability

4. System Reliability

Business Modeling Activity Diagram

Activity Diagram for reserving a book

Source – Created by Author

References

Dehraj, P., & Sharma, A. (2019). Autonomic Provisioning in Software Development Life Cycle Process. SSRN Electronic Journal. doi: 10.2139/ssrn.3349295

Kaur, A., & Kaur, K. (2015). Suitability of Existing Software Development Life Cycle (SDLC) in Context of Mobile Application Development Life Cycle (MADLC). International Journal Of Computer Applications, 116(19), 1-6. doi: 10.5120/20441-2785

Kneuper, R. (2017). Sixty Years of Software Development Life Cycle Models. IEEE Annals Of The History Of Computing, 39(3), 41-54. doi: 10.1109/mahc.2017.3481346

Mohankumar, M., & Anand Kumar, M. (2016). Green based Software Development Life Cycle Model for Software Engineering. Indian Journal Of Science And Technology, 9(32). doi: 10.17485/ijst/2016/v9i32/88499

Remember, at the center of any academic work, lies clarity and evidence. Should you need further assistance, do look up to our System Analysis and Design Assignment Help