Itec 630 Final Examination Spring 2015 Please Read These Ins

Itec 630final Examinationspring 2015please Read These Instructions Car

ITEC 630 Final Examination Spring 2015 Please read these instructions carefully. Failure to correctly follow them will adversely impact your grade. This exam is open-book, open-notes. Do not discuss any aspect of this exam with anyone else – no discussions in conferences, no emails to me.

I will grade the exams on-line, therefore: Do not include any extraneous graphics that do not directly contribute to your answer. Answer on the PowerPoint slides provided – you may add slides. Use no font smaller than 12 pitch (if I cannot read it you won’t get credit). Do not import graphics from any program besides PowerPoint (i.e. Visio).

Exam is due not later than Midnight EST Sunday 26 April. Late submissions will NOT be accepted and will earn a grade of zero. Post your PowerPoint slides in your assignment folders on LEO.

Paper For Above instruction

Question 1: (20 Points – 4 Points Each) Multiple Choice

Eliminate all but the correct answer for each question:

• Which is not a factor to consider in software evaluation?
  • A. Performance effectiveness
  • B. Performance efficiency
  • C. Ease of use
  • D. Quality of documentation
  • E. Target Operating System
• In a database, Keys are:
  • A. Data items in a record used to identify the record
  • B. Normalized
  • C. The names of database tables
  • D. Used to identify the most important attribute of an Entity
• In a relational database, Metadata:
  • A. Specifies the size in Bytes of the database tables
  • B. Describes the name given and the length assigned each data item
  • C. Describes the associative relationships between Entities
  • D. Provides the answers to queries
• Peer reviewers are the key participants in which activity?
  • A. Structured walkthroughs
  • B. Top-down testing
  • C. Six-Sigma quality checks
  • D. Rapid Application Design (RAD)
• All of the following are true about Modular Programming except:
  • A. Paying attention to the interfaces is important
  • B. Modules should be highly cohesive
  • C. Modules should contain Go-To statements
  • D. It facilitates breaking the programming into logical, manageable portions

Question 2: (20 Points)

A military information system on a base overseas tracks personnel on the base. Each military member is tracked by ID#, name, rank, and address. Each military member belongs to an organization on the base which has an organizational name, located in a building on the base and has a primary function (e.g., Communications Squadron). Each of these organizations is commanded by one of the military members.

In tracking command sponsorship, each military member may have one or more dependents. Each dependent has an ID#, name, age, and sex. Each organization on the base is involved in working issues or projects, which may be of interest to the base commander. These projects are tracked by a serial number and an origination date. The system will also track descriptions of the projects and their close-out dates.

Build an entity relationship model for the above scenario. Show all attributes and indicate all of your key attributes in red. Draw a logical data flow diagram (DFD: Context and Level 1) for placing an order based on the E-R diagram. The system must include the ability to: (1) Enter a new order, (2) Read customer master, (3) Read item record, (4) Create item order record, (5) Add order record.

Question 3: (20 points)

Ordering System: The process involves entering customer information, reading the customer master, reading item records, creating item order records, and adding orders. The diagram includes entities such as Customer, Invoice, and processes like Check Credit Rating, Update Credit File, and Dispatch Orders. Critical aspects include verifying customer credit, updating records, and dispatching products as part of order fulfillment.

Question 4: (20 Points)

This involves analyzing a structure chart related to order processing modules. The questions ask:

• How many times does the top module call each subordinate module?
• Which module contains the logic to call the Update Credit File Module?
• In what order does the executive module call subordinate modules?
• What tool would not be useful in preparing a Module Specification?

Question 5: (20 points)

Reflect on the tools and techniques learned in class for system analysis and design. List the tools in your toolbox and write a short paragraph on how you can or will apply them in your career and daily life.

End of Instructions

Paper For Above instruction

The evaluation of software and system development processes involves a comprehensive understanding of various factors that influence the success, efficiency, and reliability of the final product. Principles of database design, system modeling, structured analysis tools, and software engineering methodologies are integral in creating systems that meet organizational needs while maintaining scalability and robustness. In this paper, I will explore these themes in detail, emphasizing their relevance in contemporary system analysis and design practices.

Factors in Software Evaluation

When assessing software, it is critical to consider multiple factors to ensure that the product aligns with organizational goals and user requirements. Performance effectiveness and efficiency are essential; they determine whether the software operates correctly under expected workloads and optimally utilizes resources. Ease of use impacts user satisfaction and reduces training time, making it a vital consideration in usability testing. The quality of documentation affects maintenance and future development, as well-documented code and user manuals facilitate understanding and troubleshooting. Conversely, the target operating system, while significant, does not directly influence software quality but rather affects deployment options. Therefore, in evaluating software, performance, usability, and documentation are central, whereas target OS is more a deployment consideration.

Database Keys and Metadata

In databases, keys are fundamental components used to uniquely identify records and establish relationships between tables. A key is a data item or set of items that can identify a record uniquely within a table; for example, a student ID or employee number. Metadata, on the other hand, describes data about data; it specifies attributes such as data types, sizes, and relationships. In relational databases, metadata provides essential information about the structure of the database, including table schemas, attribute names, and data types, enabling database management systems to interpret and manipulate stored data effectively.

Peer Review and Modular Programming

Peer reviewers play a significant role in ensuring quality and adherence to standards in software development, particularly during structured walkthroughs where they examine code or design documents for errors and consistency. Modular programming advocates dividing software into discrete modules or components that perform specific functions. This approach enhances maintainability, testing, and reusability. Modules should be cohesive, focusing on a single task, and interfaces should be carefully managed. However, modules should avoid Go-To statements, which can lead to spaghetti code and reduce clarity. The primary purpose is to facilitate logical, manageable, and scalable programming structures.

Entity-Relationship Model and Data Flow Diagrams (Question 2)

The system described involves multiple entities and relationships, including military members, organizations, dependents, and projects. The ER model would involve entities such as MilitaryMember, Organization, Dependent, and Project. Keys include IDs for military members and dependents, with relationships indicating membership, command, and sponsorship. For example, MilitaryMember "belongs to" Organization, and "commands" MilitaryMember is associated with one Organization. Dependents are linked with military members through sponsorship relationships. Projects are associated with organizations involved in their development, tracked via serial numbers and dates.

In constructing the Data Flow Diagram (DFD) for placing an order, the context diagram would depict the external entities (e.g., Customer, Supplier) interacting with the system through processes like order entry, credit checking, and dispatching. The Level 1 DFD would detail the internal processes, data stores for customer and item records, and data flows among them, illustrating how data moves through the system from order initiation to fulfillment.

Analysis of Module Structure and Tools (Questions 3 and 4)

The order processing structure involves multiple modules with specific calling sequences and responsibilities. The analysis indicates that the top module likely calls subordinate modules multiple times, depending on process needs. The module responsible for calling "Update Credit File" is usually the "Check Credit Rating" module, which verifies and updates credit information before order dispatch. The execution order typically starts with "Check Credit Rating," followed by "Update Credit File," and then "Dispatch Orders," depending on the flowchart logic. Tools such as structured English, pseudocode, data flow diagrams, and flowcharts are instrumental in designing detailed module specifications, as they provide clarity and structure. However, a flowchart alone might lack the detailed logic necessary for precise implementation, making it less useful than structured English or pseudocode in this context.

Applying System Analysis and Design Tools

Throughout my academic and professional journey, I have accumulated a robust toolkit of system analysis and design tools, including Entity-Relationship modeling, Data Flow Diagrams, Structured English, Pseudocode, and Structure Charts. These tools enable systematic description of complex processes, facilitate communication among stakeholders, and ensure clarity in system specifications. In my future career, I intend to apply ER diagrams and DFDs during requirements gathering to visualize data and process flows clearly. Structured English and pseudocode will assist in developing detailed algorithms that are easy to understand and implement. Structure charts will guide the organization of modules, ensuring a logical and maintainable software architecture. Personally, these tools will help me in problem-solving, planning, and documenting solutions effectively, leading to higher quality software development and system analysis.

References

• Crow, M. M. (2017). System Analysis and Design. McGraw-Hill Education.
• Connolly, T., & Begg, C. (2014). Database Systems (10th ed.). Pearson.
• Levitan, R., & Levitan, D. (2011). Database Technologies. Springer.
• Shelly, G. B., & Cashman, T. J. (2017). Systems Analysis & Design (11th ed.). Course Technology.
• Stair, R., & Reynolds, G. (2019). Principles of Information Systems (13th ed.). Cengage Learning.
• Yourdon, E. (1989). Modern structured analysis. Prentice Hall.
• Hoffer, J. A., Venkataramani, V., & Topi, H. (2016). Modern Systems Analysis and Design. Pearson.
• DeMarco, T. (1978). Structured Analysis and System Specification. Yourdon Press.
• Zachman, J. A. (1987). A framework for information systems architecture. IBM Systems Journal, 26(3), 276-292.
• Ambler, S. (2002). Agile Modeling: Effective Practices for Extreme Programming and Rational Unified Process. John Wiley & Sons.