Q

Requirement Analysis and Cloud-based System Design Assignment Help

CTEC5711 Requirement Analysis and Cloud-based System Design Assignment Help - Avail Best CTEC5711 Requirement Analysis and Cloud-based System Design Assignment Help Service at Miracleskills!!
Previous << >> Next

Requirement Analysis and Cloud-based System Design Assignment

Assignment Title - An ATM Requirement Analysis and Cloud-based System Design

Deal with endless assignments without any hassle by getting the support of experienced professionals from the best online Diploma assignment help in the UK.

DO WANT TO HIRE TUTOR FOR ORIGINAL CTEC5711 REQUIREMENT ANALYSIS AND CLOUD-BASED SYSTEM DESIGN ASSIGNMENT SOLUTION? AVAIL QUALITY CTEC5711 REQUIREMENT ANALYSIS AND CLOUD-BASED SYSTEM DESIGN ASSIGNMENT WRITING SERVICE AT BEST RATES!

Learning Outcomes -

Learning Outcome 1 - Appreciate the essential issues of requirement engineering and system design.

Answer:  Requirement engineering and system design are fundamental to successful software development. Requirement engineering focuses on understanding and documenting user needs, ensuring the system aligns with stakeholder expectations. Key challenges include eliciting comprehensive requirements, managing changing needs, and ensuring clarity and consistency. System design, on the other hand, involves translating requirements into a detailed architectural blueprint. It addresses issues like modularity, scalability, performance, and security. Both disciplines are interconnected, as well-defined requirements are crucial for effective system design. Addressing these essential issues collaboratively is vital for delivering high-quality software solutions.

Learning Outcome 2 - Use and critically analyse advanced techniques for requirement specification.

Answer: Advanced techniques for requirement specification, such as User Story Mapping, enable a collaborative approach to capturing user needs in a visual and engaging format. Model-Driven Development (MDD) leverages domain-specific languages to automatically generate system models from high-level requirements, reducing ambiguity and improving consistency. Formal methods like Z and B offer rigorous mathematical techniques for specifying and verifying requirements, ensuring correctness and completeness. However, these techniques require specialized expertise and can be time-consuming to apply. Additionally, natural language processing (NLP) tools can aid in automated requirement extraction from textual documents, but their accuracy and reliability can vary. A critical analysis of these techniques involves considering factors like project complexity, team expertise, and the desired level of formality and precision.

Master the complexities of cloud technology with expertly crafted assignment solutions for Unit 16: Cloud Computing in Pearson Higher Nationals in Computing-your ultimate guide to seamless learning, top-tier insights, and academic success in the world of cloud computing!

Learning Outcome 3 - Perform requirements engineering and system design tasks to practically implement traceability.

Answer: To implement traceability, we must first meticulously elicit and document functional and non-functional requirements, ensuring they are clear, concise, and unambiguous. During system design, we must establish a clear mapping between requirements and design artifacts, such as use cases, class diagrams, and sequence diagrams. Traceability matrices can be used to visually represent these linkages, allowing for easy tracking of changes and ensuring that each requirement is addressed in the design. Tools like requirements management software can automate traceability, facilitating impact analysis and change management. By consistently maintaining traceability throughout the development lifecycle, we can enhance quality, reduce risks, and improve overall project visibility.

Learning Outcome 4 - Apply UML-v2.0 to analyse requirements and design system.

Answer: UML-v2.0 is a powerful tool for analyzing requirements and designing systems. Use Case Diagrams help visualize the interactions between users (actors) and the system, capturing functional requirements. Activity Diagrams model the workflow and decision points within the system, aiding in understanding the system's behavior. Class Diagrams represent the static structure of the system, defining classes, attributes, and relationships, which is crucial for system design. Sequence Diagrams illustrate the dynamic behavior of the system, showing the sequence of interactions between objects and the flow of control. By effectively using these UML diagrams, we can ensure a clear, consistent, and comprehensive understanding of both the requirements and the system design, leading to better quality and efficiency in software development.

Learning Outcome 5 - Analyse complex models and their inter-relationships.

Answer: Analyzing complex models and their inter-relationships involves a systematic approach that combines technical skills and domain knowledge. Techniques like decomposition and abstraction help break down complex models into smaller, more manageable components. Model validation and verification ensure the correctness and consistency of the model and its components. Formal methods like model checking and theorem proving can be used to rigorously analyze complex models and identify potential issues. Visualization tools can help in understanding the relationships between different components and their interactions. By effectively analyzing complex models, we can gain valuable insights into the system's behavior, identify potential risks, and make informed decisions during the design and development process.

Learning Outcome 6 - Critically evaluate systems, tools, processes and methods from the viewpoints of requirements analysis and cloud-based system design.

Answer: To critically evaluate systems, tools, processes, and methods from the viewpoints of requirements analysis and cloud-based system design, we must consider factors like scalability, reliability, security, and cost-effectiveness. Cloud-native technologies and microservices architecture offer advantages in scalability and flexibility, but they also introduce complexities in terms of security and management. DevOps practices can streamline the development and deployment process, but they require a strong understanding of automation tools and CI/CD pipelines. Requirements analysis techniques like use case modeling and user story mapping can be adapted for cloud-based systems, but additional considerations must be made for cloud-specific requirements like data security, disaster recovery, and performance optimization. By carefully evaluating these factors and selecting appropriate tools and methods, we can design and implement robust, scalable, and secure cloud-based systems.

Assessment - Automated Teller Machine (ATM) Simulator

Section 1 - Overview

An Automated Teller Machine (ATM) is a safety-critical and real-time system that is highly complicated in design and implementation. ATMs help financial institutions handle more transactions and make services more accessible to account holders, all without requiring additional staff. The core of every ATM is a motherboard that connects to a local server for software, data files, and account information.

Section 2 - General Requirements

A local bank intends to install a new automated teller machine (ATM) to allow users (i.e., bank customers) to perform basic financial transactions. The software to be designed will control a simulated automated teller machine (ATM) having a magnetic stripe reader for reading an ATM card, a keyboard and display for interaction with the customer, a slot for depositing envelopes, a dispenser for cash (in multiples of £20), a printer for printing customer receipts, and a key-operated switch to allow an operator to start or stop the machine (Figure 1). The ATM will communicate with the bank's computer over an appropriate communication link. (The software run on the bank's computer is not part of the requirements for this problem.). Each user can have only one account at the bank. ATM users should be able to view their account balance, withdraw cash (i.e., take money out of an account) and deposit funds (i.e., place money into an account).

Unlock your potential with comprehensive Systems Analysis and Design assignment solutions for F/617/2266, tailored for the OTHM Level 4 Diploma in Information Technology-expert guidance to elevate your analytical skills, streamline your studies, and achieve academic excellence!

GETTING STUCK WITH SIMILAR CTEC5711 REQUIREMENT ANALYSIS AND CLOUD-BASED SYSTEM DESIGN ASSIGNMENT? ENROL WITH MIRACLESKILLS'S CTEC5711 REQUIREMENT ANALYSIS AND CLOUD-BASED SYSTEM DESIGN ASSIGNMENT HELP SERVICES AND GET DISTRESSED WITH YOUR ASSIGNMENT WORRIES!

The user interface of the automated teller machine contains the following components:

i. A screen that displays messages to the user.

ii. A keypad that receives numeric input from the user.

iii. A cash dispenser that dispenses cash to the user.

iv. A deposit slot that receives deposit envelopes from the user.

v. A key-operated switch to allow an operator to start or stop the machine.

The cash dispenser begins each day loaded with 500 £20 bills (the provision of just one type of bill is a simplification for the study purpose of this case study). The bank wants you to develop software to perform the financial transactions initiated by bank customers through the ATM. The bank will integrate the software with the ATM's hardware at a later time. The software should encapsulate the functionality of the hardware devices (e.g., cash dispenser, deposit slot) within software components, but it needs not be concerned with how these devices perform their duties. The ATM hardware has not been developed yet, so instead of writing your software to run on the ATM, you should develop a first version of the software to run on a personal computer. This version should use the computer's monitor to simulate the ATM's screen, and the computer's keyboard to simulate the ATM's keypad.

An ATM session consists of authenticating a user (i.e., proving the user's identity) based on an account number and personal identification number (PIN), followed by creating and executing financial transactions. To authenticate a user and perform transactions, the ATM must interact with the bank's account information database (i.e., an organised collection of data stored on a computer). For each bank account, the database stores an account number, a PIN and a balance indicating the amount of money in the account. [Note: For simplicity, we assume that the bank plans to build only one ATM, so we do not need to worry about multiple ATMs accessing this database at the same time. Furthermore, we assume that the bank does not make any changes to the information in the database while a user is accessing the ATM. Also, any business system like an ATM faces reasonably complicated security issues. We make the simplifying assumption, however, that the bank trusts the ATM to access and manipulate the information in the database without significant security measures.]

Upon first approaching the ATM (assuming no one is currently using it), the user should experience the following sequence of events:

A. The screen displays a welcome message and prompts the user to enter an account number.

B. The user inputs a five-digit account number using the keypad.

C. The screen prompts the user to enter the PIN (personal identification number) associated with the specified account number.

D. The user enters a five-digit PIN using the keypad.

E. If the user enters a valid account number and the correct PIN for that account, the screen displays the main menu. If the user enters an invalid account number or an incorrect PIN, the screen displays an appropriate message and the ATM returns to Step 1 to restart the authentication process.

ORDER NEW COPY OF CTEC5711 REQUIREMENT ANALYSIS AND CLOUD-BASED SYSTEM DESIGN ASSIGNMENT AND SECURE HIGHER MARKS!

After the ATM authenticates the user, the main menu (Figure 2) should contain a numbered option for each of the three types of transactions: balance inquiry (option 1), withdrawal (option 2) and deposit (option 3). The main menu also should contain an option to allow the user to exit the system (option 4). The user then chooses either to perform a transaction (by entering 1, 2 or 3) or to exit the system (by entering 4).

If the user enters 1 to make a balance inquiry, the screen displays the user's account balance. To do so, the ATM must retrieve the balance from the bank's database.

The following steps describe the actions that occur when the user enters 2 to make a withdrawal:

A. The screen displays a menu (Figure 3) containing standard withdrawal amounts: £20 (option 1), £40 (option 2), £60 (option 3), £100 (option 4) and £200 (option 5). The menu also contains an option to allow the user to cancel the transaction (option 6).

B. The user inputs a menu selection using the keypad.

C. If the withdrawal amount chosen is greater than the user's account balance, the screen displays a message stating this and telling the user to choose a smaller amount. The ATM then returns to Step 1. If the withdrawal amount chosen is less than or equal to the user's account balance (i.e., an acceptable amount), the ATM proceeds to Step 4. If the user chooses to cancel the transaction (option 6), the ATM displays the main menu and waits for user input.

D. If the cash dispenser contains enough cash to satisfy the request, the ATM proceeds to Step 5. Otherwise, the screen displays a message indicating the problem and telling the user to choose a smaller withdrawal amount. The ATM then returns to Step 1.

E. The ATM debits the withdrawal amount from the user's account in the bank's database (i.e., subtracts the withdrawal amount from the user's account balance).

F. The cash dispenser dispenses the desired amount of money to the user.

G. The screen displays a message reminding the user to take the money.

NEVER BE CAUGHT IN PLAGIARISM, AVAIL CTEC5711 REQUIREMENT ANALYSIS AND CLOUD-BASED SYSTEM DESIGN ASSIGNMENT HELP SERVICE OF MIRACLESKILLS.COM AND SAVE HIGHER MARKS!

Advance your engineering expertise with precision-crafted solutions for Microcontroller Architecture and System Design, Unit 46: Embedded Systems-part of the HND in Engineering curriculum-designed to enhance your understanding, streamline your learning, and drive your success in the world of embedded systems!

The following steps describe the actions that occur when the user enters 3 to make a deposit:

A. The screen prompts the user to enter a deposit amount or type 0 (zero) to cancel the transaction.

B. The user inputs a deposit amount or 0 using the keypad. [Note: The keypad does not contain a decimal point or a pound sign, so the user cannot type a real pound amount (e.g., £1.25). Instead, the user must enter a deposit amount as a number of pence (e.g., 125). The ATM then divides this number by 100 to obtain a number representing a pound amount (e.g., 125 ÷ 100 = 1.25).]

C. If the user specifies a deposit amount, the ATM proceeds to Step 4. If the user chooses to cancel the transaction (by entering 0), the ATM displays the main menu and waits for user input.

D. The screen displays a message telling the user to insert a deposit envelope into the deposit slot.

E. If the deposit slot receives a deposit envelope within two minutes, the ATM credits the deposit amount to the user's account in the bank's database (i.e., adds the deposit amount to the user's account balance). [Note: This money is not immediately available for withdrawal. The bank first must physically verify the amount of cash in the deposit envelope, and any cheques in the envelope must clear (i.e., money must be transferred from the cheque writer's account to the cheque recipient's account.) When either of these events occurs, the bank appropriately updates the user's balance stored in its database. This occurs independently of the ATM system.] If the deposit slot does not receive a deposit envelope within this time period, the screen displays a message that the system has cancelled the transaction due to inactivity. The ATM then displays the main menu and waits for user input.

After the system successfully executes a transaction, the system should return to the main menu so that the user can perform additional transactions. If the user chooses to exit the system, the screen should display a thank you message, then display the welcome message for the next user.

The ATM will have an operator panel with a key-operated switch (located on the "inside the bank" side) that will allow an operator to start and stop the servicing of customers. When the switch is moved to the "off" position, the machine will shut down, so that the operator may remove deposit envelopes and reload the machine with cash, blank receipts, etc. The operator will be required to verify and enter the total cash on hand before starting the system from this panel.

You are required to -

MIRACLESKILLS.COM GIVES ACCOUNTABILITY OF YOUR TIME AND MONEY - AVAIL TOP RESULTS ORIGINATED CTEC5711 REQUIREMENT ANALYSIS AND CLOUD-BASED SYSTEM DESIGN ASSIGNMENT HELP SERVICES AT BEST RATES!

Part 1: Requirement specification (1000 words)

1. Understand the requirements, define the stakeholders of the system and present their functional and non-functional requirements.

2. Construct you own requirement specification template for the project.

3. List all identified use cases and write down at least two use case specifications in detail.

Part 2: Refinement and Traceability (600 words)

The software will be developed by using Object-Oriented Analysis and Development methodology:

1. Use normal step-wise refinement to derive class diagram(s) based on all the use cases.

2. Show a traceability analysis of all your use case models and classes. Your analysis has to be in both directions (use cases to classes and classes to use cases).

Part 3: Architecture Design (800 words)

The Model-View-Controller (MVC) framework is chosen to build the system architecture. Based upon the functional and non-functional requirements identified in Task 1, please

1. Justify why MVC architecture is suited to the ATM system design.

2. Present your MVC-based architecture design, and discuss/evaluate your architecture design.

Impressive writing with exceptional deals; what else do you want from the most reputable online HND Assignment help? Reach out to us from reliable service!

Part 4: Cloud-based ATM (1000 words)

Most of the world's 2.2 million or so ATMs today are essentially thick-client PCs, and the vast majority of them -- as much as 75 percent -- run Windows XP. Banks plan to move ATM software and operations to the cloud so that the machines can be run remotely, including all software updates at the server level. For cloud-based system development, many aspects need to be considered, for example, which service (provision) model, Infrastructure as a Service (IaaS), Platform as a Service (PaaS), Software as a Service (SaaS), you are going to choose, and which deployment (ownership) model, Public clouds, Private clouds, Hybrid clouds etc. you are going to use.

1. Identify the new requirements of the cloud-based ATMs and discuss the main issues of implementing these requirements.

2. Evaluate the MVC architecture for the design and development of the new cloud-based ATMs.

3. Discuss/justify the design and models (service model etc.) of the new cloud-based ATM system, and discuss the benefits and risks of migrating to Cloud.

Transform your database skills with expertly tailored assignment solutions for Unit 4: Database Design and Development-part of the Higher National Diploma in Computing-your pathway to mastering data structures, optimizing systems, and achieving academic success with confidence!

ENROL WITH CTEC5711 REQUIREMENT ANALYSIS AND CLOUD-BASED SYSTEM DESIGN ASSIGNMENT HELP AND HOMEWORK WRITING SERVICES OF MIRACLESKILLS.COM AND GET BETTER RESULTS IN CTEC5711 REQUIREMENT ANALYSIS AND CLOUD-BASED SYSTEM DESIGN ASSIGNMENTS!


Want to Excel in Course? Hire Trusted Writers for Help! —> https://miracleskills.com/

Lists of comments


Leave a comment


Captcha