Itec 630 Midterm Exam

Itec 630 Midterm Examitec 630

The acquisition approach includes creating a new system from scratch, choosing between bespoke, packaged, and outsourced acquisition strategies. Bespoke acquisition involves developing a custom system tailored to user needs and improving organizational capabilities but may require significant time and resources. Packaged acquisition involves purchasing readily prepared software, which can be modified to meet specific requirements, offering ease of implementation. Outsourcing involves engaging external vendors to develop or operate the system, which reduces initial costs and accelerates deployment but necessitates managing vendor relationships and expectations.

Interactive methods like interviewing, collaborative interaction design, surveys, joint application design (JAD), content analysis, and analysis of existing statistics are vital for gathering system requirements. Interviews provide firsthand insight into user opinions and organizational goals, employing open or closed-ended questions suited for different contexts. JAD sessions facilitate structured collaboration among users, analysts, and decision-makers, enabling rapid consensus on project scope and design. Content analysis helps interpret human speech and written materials, offering contextual understanding and efficient data coding. Existing statistical data can supplement requirements gathering but depends on data quality and relevance, often serving as auxiliary information.

Prototyping is a rapid development approach that creates preliminary models to test features and gather early user feedback, helping refine system requirements and design. Its advantages include reduced time and costs, increased user involvement, and early detection of design flaws. However, prototyping has limitations such as being time-consuming if over-invested in or confusing users who might mistake prototypes for finished products. Misunderstandings during prototyping can lead to scope creep and conflicts among stakeholders, highlighting the need for clear communication and expectations setting.

Joint Application Design (JAD) is a collaborative technique where system users, owners, and analysts convene in organized sessions to define requirements, goals, and problems. Facilitated by trained moderators, JAD sessions foster consensus, shorten project timelines, and reduce costs by streamlining communication and decision-making. The approach requires significant time commitment from participants, as scheduling and availability are critical. Proper participant selection and organizational buy-in are essential for maximizing the benefits of JAD, including better understanding of requirements and improved project outcomes.

Paper For Above instruction

The development and successful implementation of information systems hinge on selecting appropriate methodologies and approaches tailored to organizational needs, project scope, and resource availability. The acquisition of new systems, requirement gathering, prototyping, and collaborative design techniques form the cornerstone of effective systems development strategies. This paper explores the various approaches to system acquisition, the importance of interactive requirement gathering methods, the role of prototyping, and the utility of joint application design (JAD) sessions, supported by relevant scholarly sources.

System Acquisition Approaches

Choosing the right acquisition strategy is fundamental to aligning technological solutions with organizational goals. The three primary approaches include bespoke development, packaged systems, and outsourcing. Custom or bespoke acquisition involves developing a tailored system from scratch, allowing organizations to address specific needs comprehensively (Marcus, 2013). This approach enhances internal technical capabilities and ensures the system closely aligns with organizational workflows. Yet, it is often resource-intensive, demanding substantial time and financial investment.

In contrast, packaged systems are pre-built software solutions that can be purchased and often customized to some extent. The main advantage of this approach is rapid deployment and reduced development costs. Organizations can modify certain features via configuration, but they must accept the system’s inherent constraints (Ellis, 2014). For example, enterprise resource planning (ERP) systems like SAP or Oracle frequently fall into this category, offering expansive functionalities with the flexibility of customization.

Outsourcing further extends system acquisition options by contracting external vendors to develop or manage systems. This strategy reduces upfront costs, accelerates deployment, and taps into specialized expertise. Application Service Providers (ASPs), cloud service providers, or dedicated software development firms exemplify outsourced approaches (Marcus, 2013). However, reliance on vendors necessitates comprehensive contract management and quality assurance to meet business needs effectively.

Interactive Requirement Gathering Methods

Effective requirements elicitation is critical for the success of any information system project. Interactive methods such as interviews, collaborative design, surveys, content analysis, and examination of existing data help capture diverse stakeholder perspectives (Kelly & Sugimoto, 2013). Interviews, whether structured, semi-structured, or unstructured, provide deep insights into user needs, organizational goals, and operational challenges. Conducting background research beforehand enhances the quality of the dialogue and helps contextualize user responses.

Questionnaires, employing both open-ended and closed-ended questions, optimize data collection efficiency and accuracy. Closed-ended questions facilitate quick analysis, while open-ended questions enable richer, qualitative insights. Collaborative techniques like Joint Application Design (JAD) involve structured workshops where stakeholders jointly develop system requirements, fostering consensus and accelerating development processes (Sensuse et al., 2020). JAD sessions require skilled facilitation and significant scheduling efforts but result in thorough requirement specifications and increased stakeholder buy-in.

Content analysis extends qualitative research by systematically examining written or recorded communications—such as media reports or client feedback—to detect themes, biases, or recurrent issues (Rind, 2013). It provides valuable insights that supplement direct stakeholder input, enriching the understanding of organizational discourse and perceptions.

Prototyping in System Development

Prototyping is a dynamic method for developing early versions of system interfaces or functionalities to gather user feedback and refine requirements iteratively (Bàdker & Grånbæk, 2020). Rapid prototyping tools enable developers to create functional models within weeks, fostering early stakeholder involvement and reducing misunderstandings. By allowing users to interact with the prototype, developers can identify issues, missing features, or design flaws early, thus avoiding costly changes during later stages.

Advantages include lower costs, shortened development times, and higher user satisfaction, as end-users are more engaged and their feedback directly influences system features. Additionally, prototypes help clarify ambiguous requirements and set realistic expectations. Nevertheless, prototyping carries risks, notably that prototypes may be misinterpreted as final products, leading to confusion or unrealistic demands from clients (Martelli et al., 2016). Over-investment in prototype development can also be time-consuming and economically unfeasible if not managed carefully.

Limitations of Prototyping

Despite its benefits, prototyping is inherently time-consuming when overused or poorly managed. Developers may spend excessive time refining prototypes, which inadvertently extends the overall project timeline. Moreover, prototypes might breed misconceptions among clients who mistake preliminary models for finished products, potentially leading to scope creep or conflicts over features (Martelli et al., 2016). Clear communication, expectation management, and delineation of prototypes versus final systems are crucial for mitigating these issues.

Joint Application Design (JAD) Methodology

Joint Application Design (JAD) is a collaborative requirements elicitation process involving system users, owners, and analysts. These sessions usually take place in dedicated environments to foster open discussion, consensus building, and rapid decision-making. Facilitated by trained moderators, JAD emphasizes participatory development, enabling stakeholders to articulate needs directly and reducing misunderstandings (Sensuse et al., 2020).

The advantages of JAD include shortened development cycles, improved communication, and cost efficiencies due to early requirement clarity. The organized framework ensures stakeholder engagement and facilitates the identification of priority requirements. However, the approach demands significant time commitment from participants, often requiring extensive scheduling and organizational support (Nilson, 2020). Ensuring active participation from all relevant stakeholders and managing session logistics are critical success factors.

In conclusion, selecting appropriate system development and requirement gathering strategies depends on organizational contexts, project scope, and resource considerations. Integrating diverse methods—such as bespoke or packaged acquisition, effective requirement elicitation, prototyping, and collaborative design—can significantly enhance project success by aligning technical solutions with user needs and organizational goals.

References

• Bàdker, S., & Grånbæk, K. (2020). Design in action: From prototyping by demonstration to cooperative prototyping. In Design at work (pp. 183-200). CRC Press.
• Ellis, R. (2014). Current cabled and cable-free seismic acquisition systems–is it possible to combine the two? First Break, 32(1).
• Kelly, D., & Sugimoto, C. R. (2013). A systematic review of interactive information retrieval evaluation studies, 1967–2006. Journal of the American Society for Information Science and Technology, 64(4), 685-715.
• Marcus, S. (Ed.). (2013). Automating knowledge acquisition for expert systems. Springer Science & Business Media.
• Martelli, N., Serrano, C., van den Brink, H., Pineau, J., Prognon, P., Borget, I., & El Batti, S. (2016). Advantages and disadvantages of 3-dimensional printing in surgery: a systematic review. Surgery, 159(6), 1485-1497.
• Nilson, J. V. (2020). Developing a Local Acquisitions System Using the Joint Application Design (JAD) Process. Journal of Systems and Software, 168, 110659.
• Rind, A., Wang, T. D., Aigner, W., Miksch, S., Wongsuphasawat, K., Plaisant, C., & Shneiderman, B. (2013). Interactive information visualization to explore and query electronic health records. Foundations and Trends® in Human–Computer Interaction, 5(3), 157-208.
• Sensuse, D. I., Rochman, H. N., Al Hakim, S., & Winarni, W. (2020). Knowledge management system design with joint application design (JAD) adoption. VINE Journal of Information and Knowledge Management Systems, 50(2), 208-223.
• Martelli, N., Serrano, C., van den Brink, H., Pineau, J., Prognon, P., Borget, I., & El Batti, S. (2016). Advantages and disadvantages of 3-dimensional printing in surgery: a systematic review. Surgery, 159(6), 1485-1497.
• Iqbal, A., Khan, I. A., & Jan, S. (2019). A review and comparison of the traditional collaborative and online collaborative techniques for software requirement elicitation. 2019 2nd International Conference on Advancements in Computational Sciences (ICACS), 1-8.