Development costs are the one-time expenses incurred during the System Development Life Cycle (SDLC) to create and deploy a new information system. These costs directly encompass the salaries of the project team (analysts, designers, programmers), hardware and software acquisition for the project, and other expenses related to the initial phases of analysis, design, coding, testing, and installation. They represent the total initial investment required to bring the system from concept to operational readiness. Once the system is installed and goes live, subsequent costs are categorized as operational or maintenance costs.

A. Service cost: This typically refers to recurring fees for third-party services (e.g., cloud hosting, SaaS subscriptions) which are part of ongoing operational expenses, not the initial build phase.

B. Maintenance cost: These are recurring costs incurred after the system is deployed to fix bugs, apply patches, and provide user support, ensuring the system remains functional over time.

C. Operating cost: These are the ongoing, day-to-day expenses required to run the system after it has been installed, such as electricity, network bandwidth, and salaries of end-user support staff.

1. Valacich, J. S., & George, J. F. (2020). Modern Systems Analysis and Design (9th ed.). Pearson. In Chapter 2, "Managing the Information Systems Project," the text distinguishes between one-time and recurring costs. Development costs are classified as one-time costs associated with the project's initiation, analysis, design, and implementation phases (pp. 45-46).

2. Whitten, J. L., & Bentley, L. D. (2007). Systems Analysis and Design Methods (7th ed.). McGraw-Hill/Irwin. Chapter 4, "Feasibility Analysis and the System Proposal," explicitly defines development costs as "one-time costs that will not recur after the project has been completed," listing salaries of the project team as a primary example (p. 131).

3. MIT OpenCourseWare. (2009). 15.516: Information Technology and the Modern Corporation, Lecture 10: IT Economics. Massachusetts Institute of Technology. The lecture notes differentiate between upfront investment costs (development) and ongoing operational costs. The analysis, design, and implementation activities are categorized under the initial investment or development cost. (Available at: ocw.mit.edu)

In the context of Information Technology Management, data is fundamentally treated as a critical organizational asset. A significant portion of this data, including intellectual property, trade secrets, financial records, and customer information, is proprietary, meaning it is owned by the organization and provides a competitive advantage. This data is also often confidential, with access restricted to authorized individuals to prevent unauthorized disclosure, comply with regulations (e.g., GDPR, HIPAA), and protect privacy. Standard IT governance practices, such as data classification, exist specifically to manage and protect data based on its proprietary and confidential nature.

B. False: This is incorrect. To state that data is not often proprietary or confidential would contradict the core principles of data security, intellectual property law, and business strategy, where protecting sensitive information is paramount.

1. Laudon, K. C., & Laudon, J. P. (2020). Management Information Systems: Managing the Digital Firm (16th ed.). Pearson. In Chapter 8, "Securing Information Systems," the text explicitly discusses the need to protect "valuable proprietary information such as trade secrets, new product development plans, or marketing strategies" and "confidential personal and financial data" (p. 316).

2. University of California, Berkeley. (2023). Data Classification Standard. Berkeley Information Security Office. This official university standard outlines categories for data, including "Protection Level 3 (P3)" for data that is "highly sensitive" and whose unauthorized disclosure could have a severe adverse impact. This level includes "proprietary information" and other confidential data, demonstrating the formal recognition of this concept.

3. Tallon, P. P. (2013). Corporate governance of data: The case for a chief data officer. Proceedings of the 46th Hawaii International Conference on System Sciences, 4991-5000. This academic paper emphasizes that data is a "critical organizational asset" that requires formal governance structures for its protection and management, inherently acknowledging its valuable, and thus often proprietary and confidential, status. (https://doi.org/10.1109/HICSS.2013.155)

Object-Oriented Analysis (OOA) is most commonly structured as a five-step process. This approach provides a systematic way to analyze a problem domain and define a system in terms of objects. The five fundamental steps are:

1. Identify Classes: Determine the key objects or concepts in the problem domain.

2. Identify Attributes: Define the data or state for each class.

3. Identify Operations: Define the behavior or methods for each class.

4. Identify Relationships: Establish the connections between classes, such as association, aggregation, and inheritance.

5. Model the System: Create diagrams (like UML Class Diagrams) to represent the static structure and dynamic interactions of the objects.

This five-step framework is a widely taught and practiced standard in software engineering.

A. Three: This number is too simplistic, often failing to separate the distinct and crucial analysis activities of defining attributes, operations, and relationships.

B. Four: While some specific methodologies might propose four steps, the five-step model is more comprehensive and is the most widely recognized standard in academic and practical contexts.

D. Six: A six-step process typically includes activities like requirements elicitation or model review, which are part of the broader software lifecycle rather than the core OOA process itself.

1. Coad, P., & Yourdon, E. (1991). Object-Oriented Analysis (2nd ed.). Prentice Hall. In Chapter 1, "Object-Oriented Analysis," the authors introduce and detail their influential five-step OOA model: Identifying objects, identifying structures, identifying subjects, defining attributes, and defining services.

2. Pressman, R. S., & Maxim, B. R. (2015). Software Engineering: A Practitioner's Approach (8th ed.). McGraw-Hill Education. Chapter 8, "Requirements Modeling: Class-Based Methods," describes the activities for creating a class-based model, which align with the five core steps, including identifying analysis classes, specifying attributes, defining operations, and modeling associations and dependencies.

3. Dennis, A., Wixom, B. H., & Tegarden, D. (2015). Systems Analysis and Design: An Object-Oriented Approach with UML (5th ed.). Wiley. Chapter 5, "Structural Modeling," outlines the process of creating class diagrams by identifying classes, attributes, operations, and relationships, reflecting the core five activities of OOA.

The Systems Design Life Cycle (SDLC) is a conceptual model used in project management that describes the stages involved in an information system development project. While models can vary, a widely accepted seven-phase model is: 1. Planning, 2. Analysis, 3. Design, 4. Development (Building), 5. Testing, 6. Implementation (Installation), and 7. Operations & Maintenance. The sixth phase, Implementation or Installation, involves deploying the tested system into the live production environment. This includes activities like data migration, user training, and the physical installation of hardware and software.

A. Training: Training is a critical sub-activity that occurs within the sixth implementation/installation phase, not a standalone phase itself in this context.

C. Operations: This is the seventh and final phase of the SDLC, which begins only after the system has been successfully installed and is running.

D. Building: This refers to the development or coding phase, which is the fourth step in the SDLC, occurring well before testing and installation.

1. Florida State University, College of Communication & Information. (n.d.). The System Development Life Cycle (SDLC). LIS 2780 Course Guide. Retrieved from https://guides.lib.fsu.edu/c.php?g=1222451&p=9010501.

Reference Point: The guide explicitly lists the seven phases of the SDLC, identifying "Implementation" as the sixth phase.

2. University of Texas at Austin, McCombs School of Business. (n.d.). The Systems Development Life Cycle. Tech Articles. Retrieved from https://www.mccombs.utexas.edu/tech-articles/the-systems-development-life-cycle/.

Reference Point: This article outlines the seven phases, clearly stating that the sixth phase is "Implementation," which involves installing the system for user access.

3. Valacich, J. S., & George, J. F. (2020). Modern Systems Analysis and Design (9th ed.). Pearson.

Reference Point: Chapter 1, "The Systems Development Environment," describes the SDLC. While it presents a condensed four-phase model, the detailed breakdown shows that implementation (which includes installation, documentation, and training) follows the design and precedes the operation phase. The more granular, traditional model places it as the sixth step.

The Structured Approach, also known as structured design or functional decomposition, is a software development methodology that focuses on breaking down a system's processes into smaller, manageable units called functions or modules. The primary principle is to organize the program around the actions it performs. The system is viewed as a hierarchy of functions, where higher-level functions call lower-level ones to accomplish a task, directly aligning with the description of building programs from modules to meet functional requirements.

B. Model Approach: This is not a standard, formally defined software development methodology. The term is too ambiguous to be a correct answer.

C. Object-Oriented Approach: This approach is based on modeling the system as a collection of interacting objects, which encapsulate both data (attributes) and functions (methods), not just functions.

D. Transnational Approach: This is not a recognized term in software development methodologies and is irrelevant to the concepts of program design described.

1. Sommerville, I. (2011). Software Engineering (9th ed.). Pearson Education. In Chapter 2, Section 2.1.2, "Software engineering methods," structured methods are described as those that "use a functional viewpoint" and are based on "decomposing the system into a set of interacting functions."

2. Fairley, R. E. (1985). Software Engineering Concepts. McGraw-Hill. Chapter 5, "Design," details structured design (functional decomposition) as a primary method for deriving a modular program structure from a system's functional requirements (pp. 168-175).

3. University of Texas at Austin, Department of Computer Science. (n.d.). CS 373: Software Engineering - Notes on Design. Retrieved from course materials which describe Structured Analysis/Structured Design (SA/SD) as a top-down functional decomposition method focusing on processes and data flows between them.

The System Development Life Cycle (SDLC), which governs the process of system analysis, follows a structured sequence of phases. The typical initial steps are (1) Problem Identification and Preliminary Investigation, followed by (2) a Feasibility Study to assess the project's viability. The third major step involves a detailed analysis of user requirements and the design of the system's technical architecture. While Analysis and Design are distinct phases, they are deeply interconnected and represent the core technical phase where the problem is understood in detail (Analysis) and the solution is blueprinted (Design). This combined phase logically follows the initial investigation and feasibility assessment.

A. Feasibility Study: This is an earlier step, typically the second in the process, conducted after initial investigation to determine if the project should proceed.

B. Select an Alternative: This is a decision-making sub-task that occurs within the analysis or design phase, not a distinct, high-level phase itself.

C. Recommendation Review: This is a management or governance activity, often occurring after the analysis and design are proposed, rather than a core step in the development process.

1. Valacich, J. S., & George, J. F. (2020). Modern Systems Analysis and Design (9th ed.). Pearson. In Chapter 1, the SDLC is outlined with the following phases: 1. Planning and Selection, 2. Analysis, 3. Design. This sequential model places the Analysis and subsequent Design phases after the initial planning, confirming they constitute the core steps following preliminary stages.

2. Laudon, K. C., & Laudon, J. P. (2016). Management Information Systems: Managing the Digital Firm (14th ed.). Pearson. Chapter 13, "Building Information Systems," describes the traditional systems lifecycle. The process begins with Systems Analysis (which includes the feasibility study) and is immediately followed by System Design. This establishes the sequence where design is the next major phase after the initial analysis is completed.

3. Dennis, A., Wixom, B. H., & Roth, R. M. (2015). Systems Analysis and Design (6th ed.). John Wiley & Sons. The textbook presents the core phases of the SDLC as Planning, Analysis, Design, and Implementation (Part One: Foundations for Systems Development). This structure confirms that the Design phase is the third major phase in the development process.

Functional design, also known as logical design, focuses on specifying what a system will do based on user requirements, without detailing the implementation. This process logically begins by defining the desired outputs (e.g., reports, screen displays, data files). The outputs represent the primary goal and purpose of the system from the user's perspective. Once the outputs are clearly specified, the necessary inputs and processing steps required to produce those outputs can then be determined and designed. This output-driven approach ensures the system is built to meet its core objectives.

B. Organizational design: This is incorrect because it pertains to the structure of an organization, including roles, responsibilities, and hierarchies, not the design of an information system.

C. Object-Oriented design: This is incorrect as it begins by identifying objects, their attributes, and their behaviors within the problem domain, rather than starting with the system's final outputs.

D. Structured design: This is incorrect because it is a methodology for translating a pre-existing functional specification into a physical program structure. It uses the outputs defined during functional design but does not begin with their specification.

1. Shelly, G. B., Cashman, T. J., & Rosenblatt, H. J. (2011). Systems Analysis and Design (9th ed.). Cengage Learning. In Chapter 8, "Output and User Interface Design," the text emphasizes the primacy of output design: "Because outputs are the most visible and critical part of the system, some analysts believe that output design is the most important task of all. The design process starts with the outputs..." (p. 314).

2. Awad, E. M. (2007). Systems Analysis and Design (2nd ed.). Galgotia Publications. The book describes the logical design phase (functional design) and typically presents the design of system outputs as the first and most critical step. "The design of computer output is the most important...phase of the systems design. The project team's main objective is to design a system that serves users' needs. Since output is the only visible system product, it is the main basis for the justification and evaluation of the system." (Paraphrased from Chapter 10).

3. University of Texas at Austin, McCombs School of Business. (Courseware for MIS 373: Systems Analysis and Design). The course materials describe the logical design phase, stating: "The process of designing the system's logic is often called logical design (or functional design)... The first step is to design the system outputs." This explicitly links the beginning of the functional design process with the specification of outputs.

Explicit knowledge is knowledge that can be easily articulated, codified, stored, and transmitted to others. It is formal and systematic. Facts, data, manuals, procedures, and scientific formulas are classic examples of explicit knowledge because they are objective pieces of information that can be written down in documents, stored in databases, and shared without ambiguity. This type of knowledge represents the "know-what" and is directly represented by factual statements.

B. Tactic Knowledge: This is a common misspelling of Tacit Knowledge, which is personal, experiential, and difficult to articulate or formalize, such as intuition or "know-how."

C. Business Knowledge: This is a broad category that encompasses both explicit knowledge (like sales figures) and tacit knowledge (like understanding market sentiment), making it less precise.

D. Strategic Knowledge: This relates to an organization's long-term goals and competitive plans. It is a high-level application of knowledge, combining both explicit data and tacit insights.

1. Nonaka, I., & Takeuchi, H. (1995). The Knowledge-Creating Company: How Japanese Companies Create the Dynamics of Innovation. Oxford University Press. In Chapter 3, "The Spiral of Knowledge," the authors define explicit knowledge as knowledge that "can be expressed in words and numbers and shared in the form of data, scientific formulae, specifications, manuals and the like" (p. 59). This directly aligns facts with explicit knowledge.

2. Alavi, M., & Leidner, D. E. (2001). Review: Knowledge Management and Knowledge Management Systems: Conceptual Foundations and Research Issues. MIS Quarterly, 25(1), 107–136. On page 111, the authors state, "Explicit or codified knowledge refers to knowledge that is transmittable in formal, systematic language." They contrast this with tacit knowledge, reinforcing that facts fall under the explicit category. DOI: https://doi.org/10.2307/3250961

3. Polanyi, M. (1966). The Tacit Dimension. University of Chicago Press. Polanyi's foundational work distinguishes between explicit knowledge (that which can be articulated) and tacit knowledge ("we can know more than we can tell"), establishing the conceptual basis for why facts, which are tellable and recordable, are not tacit. (See Chapter 1, "Tacit Knowing").

In object-oriented programming and design, a class serves as a blueprint or template for creating objects. It defines a common structure (attributes) and behavior (methods) that represent a real-world concept or thing. For example, a class named Car would define the general properties of all cars. Specific, individual cars (e.g., a red Toyota with a specific VIN) are then created as instances, or objects, of the Car class. Therefore, a class is the representation from which multiple specific instances are derived.

B. Procedures: A procedure is a sequence of programming instructions that performs a specific task. It represents an action or process, not a template for creating instances of a thing.

C. Object: An object is a single, concrete instance of a class. It is one of the "specific instances" but not the general representation or blueprint for all such instances.

D. Links: A link represents a connection or relationship between objects. It does not represent the "thing" itself but rather the association between instances.

1. Object Management Group (OMG). (2017). Unified Modeling Language (UML) Specification, Version 2.5.1.

Section 9.2.4, Semantics - Classes: "A Class describes a set of objects that have the same features (attributes and operations). An object is an instance of a Class." This official standard defines a class as the descriptor for a set of object instances.

2. Guttag, J. V. (2013). Introduction to Computation and Programming Using Python. MIT Press.

Chapter 8, Section 8.1, Abstract Data Types and Classes: "A class is a collection of data and a set of methods for operating on that data... An object is a particular instance of a class." This university-level text clearly distinguishes a class as the template and an object as the instance.

3. Booch, G., Rumbaugh, J., & Jacobson, I. (2005). The Unified Modeling Language User Guide (2nd ed.). Addison-Wesley Professional.

Chapter 5, Classes: "A class is a description of a set of objects that share the same attributes, operations, relationships, and semantics. An object is an instance of a class." This foundational text on software modeling reinforces the definition.

The Systems Design Life Cycle (SDLC) is a conceptual framework for managing the creation or alteration of information systems. While the exact number of steps can vary between different models (e.g., 7-phase vs. 10-phase), they follow a consistent logical progression. In a detailed, granular SDLC model, the sequence proceeds from analysis and design to building and testing. The "Conversion" step, which involves migrating data and switching from the old system to the new one, is a critical part of the implementation phase. This phase occurs after all development and testing are complete but just before the system enters its final, ongoing "Operations" and maintenance phase. Therefore, in a detailed 10-step model, Conversion is logically positioned as the ninth step.

B. Building: This is the development/coding stage, which occurs in the middle of the life cycle, well before final implementation steps like conversion.

C. System Analysis: This is one of the earliest phases, focused on gathering and defining requirements, happening long before the system is built or converted.

D. Operations: This is the final, ongoing phase of the SDLC where the system is actively used and maintained, occurring after the conversion is complete.

1. Satzinger, J. W., Jackson, R. B., & Burd, S. D. (2012). Systems Analysis and Design in a Changing World (6th ed.). Cengage Learning. In the described six core processes, Process 6, "Deploy the System," explicitly includes the activity of "Convert existing data." This process immediately precedes the final process, "Support the System" (Operations). (See Chapter 1, Figure 1-6, "The six core processes of the SDLC").

2. Valacich, J. S., & Schneider, C. (2014). Information Systems Today: Managing in the Digital World (6th ed.). Pearson. The text describes the "Systems Implementation" phase as including activities like programming, testing, and installation. The installation activity is detailed as involving "converting data from the old system to the new system." This phase follows design and precedes the final "Systems Maintenance" phase. (See Chapter 11, "Developing and Acquiring Information Systems," Section: "Phase 4: Systems Implementation").