I am in week 9 and I need help. Create requirement specifications, design specifications, and processing models (including input/out tables, data flow models, and procedural processing).

First of all what do each of these terms mean? That is all I need to know I am in Axia college and I know that you do not have their materials but if you could explain what exactly they are looking for that would be a great help.

But what is the School Subject? IT/210 does not tell me.

Sra

Currency conversion project if you need something specific let me know my instructer is not much help with this.

FUNDAMENTALS OF PROGRAMMING WITH ALGORITHMS AND LOGIC (

So you are working on a project for currency conversion.

Imagine you are the manager of a financial firm, and you need to hire a consulting firm to do the job. What would you put in the requirements document to make sure you get what you need?

What would you accept in terms of the design, how many and which currencies do you need, how do the conversion rates get updated....

Look up your text book to find out the definition of these terms, and see if you can come up with some proposed response.

We'll be glad to help you refine your response.

I figured out all of them except for procedural processing I cannot find the definition for this in my reading and my instructor keeps saying please see the assignment below others in the class have also asked him with the same result. I could not even begin to come up with an answer for it.

Procedural processing refers usually to a language where the action is executed linearly, one instruction after another, unless there are loops or branches. Examples are C, C++, Fortran and Basic.

With modern user-oriented languages, processing is according to the user-interaction such as the movement of a mouse, a mouse-click, keyboard, etc. This is called event-driven processing.

Certainly! Here's an explanation of the terms you mentioned:

1. Requirement Specifications: This refers to a document that outlines the specific functionalities or features that a software system or application should possess. It includes a detailed analysis of the requirements gathered from stakeholders and users.

To create requirement specifications, you'll typically follow these steps:
- Gather requirements: Meet with stakeholders and users to understand their needs and expectations.
- Define requirements: Document the gathered information in a structured manner, specifying what the system should do, what data it should handle, and any constraints or limitations.
- Organize requirements: Group requirements based on their related functionalities or themes.
- Review and validate requirements: Engage stakeholders to ensure that the documented requirements align with their expectations.

2. Design Specifications: This term refers to a document or set of diagrams that articulate how the software system will be structured and function. It includes the architecture, data models, user interfaces, and other technical details necessary to guide software development.

To create design specifications, you can follow these steps:
- Identify system components: Analyze the requirements and determine the major building blocks necessary for the system.
- Define the architecture: Determine how the different components interact, communicate, and collaborate to achieve the desired system functionality.
- Design the user interface: Specify how users will interact with the system, including screen layouts, navigation, and functionality.
- Create data models: Develop a schema that represents the system's data and relationships, often using diagrams like entity-relationship diagrams or class diagrams.

3. Processing Models: This term refers to the representation of how data and information flow through a system, including input/output tables, data flow diagrams, and procedural processing steps.

To create processing models, you'll typically follow these steps:
- Create input/output tables: Identify the different inputs that the system will receive and the corresponding outputs it will produce. Document these relationships in tabular format.
- Develop data flow diagrams: Illustrate the flow of data within the system, showing how information moves from input to output through various processes or modules.
- Document procedural processing: Specify the steps, algorithms, or logic that the system will follow to process the input and produce the desired output. This can be represented using pseudocode, flowcharts, or process diagrams.

Remember, the exact requirements and specifications may vary based on your specific project or course requirements. It's important to follow any guidelines or instructions provided by Axia College or your instructor.