Question

(My Name is AA please I need new and unique answers, please. (Use your own words, don't copy and paste),Please Use your keyboard (Don't use handwriting)

((Thank you FOR YOUR HELP))

SUBJECT: System analysis and design IT243

Q1:

Assume the following scenario:
A small company needs to develop an information system for the Finance and Accounting Department. As an analyst which process model would you prefer and why?

Answer 1

For a small company that needs to develop an information system for Finance and Accounting department, as an analyst, i prefer the linear sequential model (Waterfall model).

The linear sequential model sometimes called the classic life cycle or the waterfall model suggests a systematic, sequential approach to software development that begins at the system level and progresses through analysis, design, coding, testing and support. The waterfall is the one of the most common and traditional methodologies used in project management. The waterfall model is commonly used in small projects where all the requirements are defined and there is no scope for change in the requirements.

The waterfall model encompasses the following activities:

1. System/ information engineering and modeling: Because software is always part of a larger system, work begins by establishing requirements for all system elements and then allocating some subset of those requirements to software. This system view is important when software must interact with other elements such as hardware, people and database system engineering and analysis encompass requirements gathering at the system level with a small amount of top level design and analysis.

2. Software requirements analysis:

In this phase, design, function, purposes are understood and the requirements are recorded. Here, the specifications of the input and output or the final product are captured in product requirement specification document. Requirements for both the system and the software are documented and reviewed with the customer.

3. System Design − The requirement specifications from first phase are studied in this phase and the system design is prepared. This system design helps in specifying hardware and system requirements and helps in defining the overall system architecture.

Software design is actually a multistep process that focuses on four distinct attributes of a program: data structure, software architecture, interface representations and procedural details.

4. Code generation: The design must be translated into a machine readable for. The code generation step performs this task. If design is performed in a detailed manner, code generation can be accomplished mechanically.

5. Testing: Software Testing is a procedure of finding defects to guarantee that the system being developed meet the requirements. This process assures quality and optimized efficiency. You need to run tests on every form, every script, run a spell-checking software to remove every possible type. Use code validators to examine the code follow the latest web standards.

6. Support/ Maintenance: Software will undoubtedly undergo change after it is delivered to the customer. Changes will occur because errors have been encountered and the software must be adapted to accommodate changes in its external environment, or the customer requires functional or performance enhancements. There are some issues which come up in the client environment. To fix those issues, patches are released. Also to enhance the product some better versions are released. Maintenance is done to deliver these changes in the customer environment.

Benefits of Waterfall Methodology in this project (Information system for Finance and Accounting department)

1. Easy to Follow:
Waterfall requires all the requirements to be well defined and therefore they could be easily understood by anyone working on the project

2. Cost-effective:

Since the projects are easier to complete under waterfall project management. That’s the reason they likely take less time in execution and in meeting the deadline successfully. There are very few chances of finding bugs, errors or complicated problems during the planning, designing, testing and the final end of the project. The companies merrily go for the linear sequential methodology for smaller projects. They take less time, fewer developers and fewer resources to complete. It is also less pricey because the companies don’t need to use expensive technology and machinery to complete such software programs.

3. Suitable for different geographical positions:

Communication and remote projects become a major hurdle for larger and complicated projects. Waterfall projects are smaller and flexible ones are highly applicable for remote geographical positions. As such products can be developed by a smaller team and don’t need much communication to resolve the errors.

4. Its linear:

It has linear sequential patterns which make it flexible to follow the Waterfall Methodology. The sequential projects don’t need much changing once the project has started the development. Waterfall methodology suits better for the smaller projects where demands are clear and understandable. The linear sequential model in software engineering requires proper documentation for each developing aspect..

5. Less time consuming:

A standard problem is to reach timeline goals, at the expense of conducting business growth activities. The unexpected errors and delay waste resources, money and time. Waterfall Methodology projects don’t require much changing as they follow a linear sequence. That’s the reason they are delivered on time.

6. Customer satisfaction:

Waterfall methodology is the best approach to follow, if the customer is clear regarding the needs of the software, as the linear sequential methodology is less time taking and less costly.

7. Privacy and security:

It ensures privacy and security. It supports security during the execution of the program.

These are the reasons why i prefered waterfall model for the development of this project.