StudyCorgi Tech & Engineering

Information System Development: From Scratch to Guide

Introduction

In all cases of developing an information system from the ground up, it is vital to create an IRD strategy to guide the development process. The system model not only expresses requirements but also provides an informal description of data points and allows for the definition of logical architecture, which will encompass functional requirements and non-functional needs. The requirement modeling strategy that would be the best to adopt in this scenario is a structured analysis that uses a data-oriented approach to conceptual modeling.

We will write a
custom essay
specifically for you

for only $16.05 $11/page
308 certified writers online
Learn More

Project Management Case Study

Before beginning a project, it is necessary to identify the requirements analysis strategy. Since Bev’s Barricades has no existing system in place, an outcome analysis seems best. An outcome analysis focuses on fundamental outcomes that provide value to the company and its customers (Dennis, Wixom, & Tegarden, 2015). For Bev’s Barricades, the outcome is to provide equipment to its clients that efficiently fit their needs. However, to meet this goal, it is necessary to undergo a series of processes, ranging from payment processes to inventory management and logistics that the owner would like to be present in the information system.

It is viable to create a strategic matrix that provides relevant context and enables the facilitation of vertical processes in an organization while offering a level of consistency. A matrix includes a self-contained strategy that outlines principles of integration and governance. Each process area of the company should be considered in the context of independent management and information resources, with each potentially having a sub-strategy. A strategic matrix allows the creation of parallel strategies for each department, with tools and activities that feedback to the core process strategy and management framework.

A fitting team-based technique to use would be joint application development (JAD), which allows for interaction between the project team, management, and users to identify key requirements for the information system. It is a comprehensive method for collecting information that enables the project development team to accurately identify system specifications from end-users to avoid potential complaints or dissatisfaction in the future.

Participants in JAD sessions should include managers from each relevant department outlined by Bev’s Barricades such as inventory, accounting, design, marketing, IT support, and logistics. A facilitator should be present as well to facilitate the process in a streamlined manner (Dennis et al., 2015). Although more expensive and time-consuming, this approach is necessary considering that there is no existing infrastructure in place and the system must fit the custom requirements of the business.

Conclusion

Information collection is a critical process in an IRD strategy. The best elicitation techniques of user requirements in the case of Bev’s Barricades will be interviews and observation. The selected interviewees should be from various employee levels within the company who can provide key specifications and viewpoints on the system. For example, in accounting, it may be necessary to interview the department head to identify the strategic vision, a manager for common problems in day-to-day operations, and a data entry clerk as a regular end-user of the information system. A similar approach should be used with each department identified by Bev’s Barricades that will be served by the future information system.

Interview questions should be both close-ended, to gather precise information on data analytics, and open-ended, to provide subjective information on user preferences (Dennis et al., 2015). At the same time, observations should be performed on any processes that are brought up during the interview. Observation offers the opportunity for deeper insights into practices and patterns of an organization, as well as serving as a vital supplement elicitation technique to interviews.

Get your
100% original paper
on any topic

done in as little as
3 hours
Learn More

Reference

Dennis, A., Wixom, B. H., & Tegarden, D. (2015). Systems analysis and design: An object-oriented approach with UML (5th ed.). Hoboken, NJ: Wiley.

Print Сite this

Cite this paper

Select style

Reference

StudyCorgi. (2021, March 4). Information System Development: From Scratch to Guide. Retrieved from https://studycorgi.com/information-system-development-from-scratch-to-guide/

Work Cited

"Information System Development: From Scratch to Guide." StudyCorgi, 4 Mar. 2021, studycorgi.com/information-system-development-from-scratch-to-guide/.

1. StudyCorgi. "Information System Development: From Scratch to Guide." March 4, 2021. https://studycorgi.com/information-system-development-from-scratch-to-guide/.


Bibliography


StudyCorgi. "Information System Development: From Scratch to Guide." March 4, 2021. https://studycorgi.com/information-system-development-from-scratch-to-guide/.

References

StudyCorgi. 2021. "Information System Development: From Scratch to Guide." March 4, 2021. https://studycorgi.com/information-system-development-from-scratch-to-guide/.

References

StudyCorgi. (2021) 'Information System Development: From Scratch to Guide'. 4 March.

Copy to clipboard

This paper was written and submitted to our database by a student to assist your with your own studies. You are free to use it to write your own assignment, however you must reference it properly.

If you are the original creator of this paper and no longer wish to have it published on StudyCorgi, request the removal.

Psst... Stuck with your
assignment? 😱
Susan
Online
Psst... Stuck with your assignment? 😱
Do you need an essay to be done?
Yes
What type of assignment 📝 do you need?
Yes
How many pages (words) do you need? Let's see if we can help you!
Yes