Sample ITECH7410 Software Engineering Methodologies Assignment

ITECH7410 Software Engineering Methodologies Assignment Sample

Final Seminar Requirements

The purpose of this assessment is to provide students with the opportunity to apply knowledge and skills developed during the semester and to demonstrate knowledge skills and expertise regarding Software Engineering Methodologies. Students must prepare their seminar content individually, but present in groups of four.

As part of the coursework and assessment in this course, students have had the opportunity to familiarize themselves with quality assurance, metrics, requirements analysis, specification, modelling, and design using formal software engineering techniques and tools. Students have also conducted research into the techniques and methods that could be applied to the software engineering tasks involved in design of a Smart City. Consistent with international standards in software engineering, it is important that software engineers take a holistic approach when considering a new project. They therefore should include processes for quality assurance, verification and validation in the methodologies adopted for a particular project.

The learning outcomes of this course require that students develop and demonstrate the following skills:

• Critically analyse and use complex decision making to research and determine the appropriate Software Engineering tools and methodologies to utilize for a given situation

• Apply professional communication skills to support and manage the engineering of a large software system

• Review, critically analyse and develop artefacts to define processes for quality assurance, risk management, and communication in large software development projects

• Implement quality assurance activities in order to verify user requirements and validate design decisions.

• Analysis of a large system development problem to decide upon the best methodological approach.

• Development of appropriate artefacts to support and manage the software engineering process such as change control and configuration management.

In this seminar, each student needs to focus on a different aspect of the Smart City software engineering development project. For their chosen aspect, they should consider the appropriate methodologies and tools that should be used to approach the engineering of a solution. Students are not asked to prepare a complete solution but are asked to describe what would be required in terms of work processes and artefacts that would be produced. The submitted report and presentation should outline how the chosen artefacts and processes would ensure quality in the final solution. For example, a student may be focused on education in a smart city. The student would need to explain the model/s that would be used relating to education in smart city.

Each student individually should prepare a professional level report in which they outline the methodology including processes, tools and modelling techniques that they recommend for their area of focus. This report should include references to appropriate literature to justify decisions made. Additionally, students should provide example artefacts to demonstrate what would be expected in the project itself.

Each group of 4 students should prepare a 20-minute seminar (5 mins each student) in which they will present their proposal to the class. This presentation should be appropriate for an audience of high-level executives who would be the stakeholders responsible for sponsoring this project. Students should include demonstration of the types of artefacts that would be created and justify how the proposed methodology is appropriate.

Each group can choose the focus area based on previous work each member has already completed. It is important that each student work on a unique aspect of the Smart City project.

Requirements

Students must record and present a seminar presentation as a panel discussion. Each student’s contribution must address their focus topic and must be based on their individual report. This content must be based on some research of recent (within 5 years) literature in academic peer reviewed journals and conferences relating to software engineering. The seminar will be presented by groups of 4 with each student taking responsibility for their particular focus topic. Each student will be individually assessed based on the material they present.

The broad topic of the seminar is What methodology is appropriate for the analysis and design of a complex Internet of Things system to be implemented to create a Smart City’s;.

Assessment Details

This assignment will be assessed by the lecturer. The assignment requires that students address the requirements outlined below.

Assessable Tasks/Requirements

Students are to provide both an individual report containing their content and reference material and the group is expected to submit a recorded seminar presentation.
Each student is expected to individually submit to Turnitin a report that they have individually prepared, particular to their specific sub-system and topic relating to Internet of Things and an implementation of a Smart City. Each group is to prepare a cohesive seminar discussion in which each student presents:

• The focus area of their seminar contribution i.e. the problems that they have focused upon

• What methodology would be appropriate to this topic. This approach must be justified and must describe the steps involved

• What artefacts would be produced in analysis and design. Examples must be provided of each artefact relating to the topic

• How the requirements would be validated

• How quality would be assured in the engineering of the system

Solution

Introduction

As part of this report, the design and analysis of a real-time money transfer system for a smart city will be carried out. This report will be a component of an assignment in which will analyse and create a control system. The construction of the control system will be the primary emphasis of the project. In conjunction with the duty of establishing a control system that has been delegated to us, this will be carried out. This examination of the real-time software system will include not only the data that is essential to the inquiry but also the control and process specifications that will be implemented into the system. (Alam, 2019)

This part of these communities is an absolute necessity due to the fact that the vast majority of the essential services that are provided to inhabitants in smart cities demand some form of payment. As a result, these communities must also have this component. These fundamental services are the engine that drives everything else, including the spending of companies on goods and services, the pay of employees, the spending of consumers, and the revenue of the government. The number of municipalities that have recently come to the realisation that the installation of cutting-edge payment technology is crucial to the notion of the intelligent city has recently increased. This realisation has come about as a result of recent events. Digital payments have the ability to facilitate a wide variety of citizen-to-government interactions (also known as C2G transactions), including toll and transit, transportation, water, education, tourism destinations, welfare care, healthcare, CFC centres, fines, and public convenience. (Wohlin C. R., 2020)

It is also feasible for it to include a wide variety of other types of payments made by the government to its residents. Some examples of these types of payments include pensions, subsidies, grants, and scholarships. These applications are causing a decrease in the need for currency, which, in turn, results in increased productivity and security. However, widespread adoption encounters obstacles not only from within but also from outside the organisation. Now that we have that out of the way, shall we take a closer look at each of these obstacles? (Digiplay Guru, 2020)

Methodology

The IoT, as has been noted, increases communication between objects with minimal human involvement. This quality is highly sought after by retailers because it simplifies the purchasing experience for customers. Internet-of-Things (IoT) payments involve the transmission of funds via a device linked to a financial account. To prepare the groundwork for the technological solution, the usage view details the user's flow through each stage of the use case. Both the human and mechanical participants in the action would be visible in this perspective. The usage view additionally provides a description of the use scenario from the user's and the system's perspectives. If this case study is applied, then every newbie has a significantly better probability of being pleased with IoT payment. As the number of people making IoT payments grows, so will the amount of data available for analysis.

Here is the process and methodology of using agile for the real time money transfer for assignment help.

The state-of-the-art method relies on a modular, end-to-end Financial Services platform that provides businesses with plug-and-play access to bank loans, personal finance management, and customer on boarding solutions via Australia's most advanced and reliable CDR Gateway, allowing for rapid deployment of Open Banking-powered use cases.

Digital payments have the ability to facilitate a wide variety of citizen-to-government interactions (also known as C2G transactions), including toll and transit, transportation, water, education, tourism destinations, welfare care, healthcare, CFC centres, fines, and public convenience. It is also feasible for it to include a wide variety of other types of payments made by the government to its residents. Some examples of these types of payments include pensions, subsidies, grants, and scholarships. These applications are causing a decrease in the need for currency, which, in turn, results in increased productivity and security. However, widespread adoption encounters obstacles not only from within but also from outside the organisation. Now that we have that out of the way, shall we take a closer look at each of these obstacles? (Hong, 2020)

Artefacts

DFD Level I (Risk Management and Quality Assurance)

In this step, there are also phases that are implemented by humans, and their purpose is to check whether or not the setup is correct before continuing. On Level 1 of the DFD, we are shown the process that is carried out by each direct entity in the RMT system. This method consists of checks at each level to ensure that the previous one was completed correctly before moving on to the next. The preceding diagram breaks the process of authentication down into its four primary steps: authenticating the user, authenticating the receiver, authenticating the OTP, and authenticating the transaction. (Park, 2019)

• Verification of User
• Verification by OTP
• Verification of Receipt
• Verification of Transaction

DFD Level II (Risk Management and Quality Assurance)

Users demonstrated each RMT scenario while doing fundamental activities at the DFD2 level. It provides a comprehensive description of the process by defining each stage in terms of the entire control, and data flow included within the system, in addition to describing the relationship between the present state and the dates that came before and after it. For example, the User verification state of the DFD 2 level compares the credentials provided by the user to those stored in the database to determine whether or not they match. If the credentials match, the RTM procedure moves on to the next stage; otherwise, it comes to an end. (Li, 2019)

• Verification of User Account
• Verification of OTP
• Verification of Transaction

Validation

Process Specifications

Login

Choose Transfer Money Option

Selecting Existing Receiver

Selecting New Receiver

Requesting Confirmation Code

Control Specifications

The "Control Specification," also known as the "CSPEC," specifies the processes that the software device is anticipated to carry out in response to an occurrence or signal. When an event occurs, the system will show the appropriate procedure that was activated as a consequence of the occurrence of the event. There are two components that are utilised when attempting to portray the overall control and data flow of the software system. (Wohlin C. R., 2020)

The Process Activation tables contain information that was gathered by directly examining the state transition diagram. This information can be accessed in those tables. This number indicates that the processes connected to the data flow model have been initiated when a given event has taken place, as demonstrated by the fact that they have begun. There is a manual that is at the designers' disposal, and they can use it to guide their work. However, it does go into detail on how the system responds to occurrences, which is included in the specification. The control specification for software does not go into depth on how the system functions or what procedures are set into motion when an incident occurs. (Peretz Shoval, 2020)

Discussion

This document also provides an overview of the fundamental procedure and entities that need to be stated and depicted in this submission. Specifically, the application is known as Draw.io, which is utilised during the process of developing such diagrams. Draw.io is a piece of open-source software that is not only uncomplicated but also straightforward and easy to understand how to use. With the assistance of the capability to drag-and-drop, we are able to get it up and running, and there are no complicated setup procedures that are required. (Li, 2019)

Data Flow Diagram

Data Flow Diagrams, often known as DFDs after their more frequent abbreviation, are graphical representations of the flow of information and data within a piece of software. It does not demonstrate where the data is located inside the system; rather, it demonstrates how the data works within the system. It does not reflect the location of the data in the system. The major objective of a DFD, which was designed specifically for the purpose of carrying out this activity, is to present the capabilities of a piece of software. The same objective can be achieved with the use of data flow diagrams (DFDs). A DFD can provide a graphical representation of all of the requirements for the system in a single, easily accessible area. This is a fantastic example that demonstrates how well-suited some software systems may be to the task of data processing. A graphic representation of the flow of information for the approach that has been suggested can be found down below. (Stankovski, 2020)

A graphical representation that can be used to describe the stages of software development cycles is known as a data flow diagram (DFD). By employing a DFD, it is possible to ascertain what subtypes of software a system and the operations it carries out must have in order to function properly. In addition to this, it formalises the architecture of the operational software as well as the flow of information throughout the system. (Stefanini, 2020)

The information that was gathered from the system that was described can be observed in the figure that can be found right after the table in this section. "Log In," "Transfer," "Identity Verification by Choosing," and "Client Payment" are the names of the three processes, with the login information being held in a third database. In order for a user to use the system, they will first need to log in with their credentials (username and password). After the customer has determined which account should receive the funds and how much money should be sent, as shown in the diagram, the client can start the process of transferring money after making those determinations. (Peretz Shoval, 2020)

Control Flow Diagram

One type of diagram that graphically depicts the control flow of a machine is known as a control flow diagram (CFD). For the very first time, engineers in the 1950s were given the opportunity to depict the processes that dictated a product visually. This development was a significant step forward in the field. Control flow diagrams have the potential to include a broad variety of different components, such as if-then-else branches, loops, and case conditions, among others. In this example, we see how a geometric diagram can not only be used to depict the various steps that are involved in a process and the details that are associated with each step but it can also be used to show how one step leads to the next step in a logical progression. This is demonstrated by the fact that a geometric diagram was used to show how one step leads to the next step in the process. Utilizing the diagram in this manner is one way to accomplish this task. The control flow that is supposed to be used for the device is illustrated in the schematic that can be found further down on this page. (Thales, 2020) The procedure that users must go through in order to access the system is depicted in the following diagram in the form of an illustration. If the user name or password is entered successfully, the user will be taken to the forwarding interface. If one of these is entered incorrectly, the user will be taken to the sign how it feels to be a user of the service. The next step in the process is for the client to begin the money transfer by either selecting a payee from their list of saved payees or manually entering the payee's account number along with the amount that they desire to send. This step marks the beginning of the second stage of the procedure. The transaction will begin as soon as the user makes their pick if the user chooses a recipient who has already enrolled for the service. Before the transaction can be executed in any other situation, the customer is needed to complete the OTP authentication process in its entirety. As evidence that the transaction was carried out correctly, the customer can be given a receipt as a confirmation that the transaction was completed successfully. (Basham, 2017)

Conclusion

Before I started my study of the anticipated needs of the system, I did some research into the effectiveness of a real-time money transmission system. This was done before I started my analysis. My work on the logical structure of the software began with me determining all of the entities and the connections that existed between them. This was the first phase of my work. In order to discover the relevant entities and their relationships, which should both be incorporated into the approach that was presented, I carried out an analysis of the system. This allowed me to determine the pertinent entities. The process of conducting research for this paper allowed me to amass a considerable amount of knowledge concerning the inner workings of real-time money channels, which I will discuss in this article. During the course of creating the data flow diagram and the control flow diagram for the proposed system, I came across certain questions concerning the anticipated operation and data flow of the proposed system. (Wohlin C. R., 2020)

Users begin the process of signing in by providing their login information, which often includes a username and a password. Once this information has been provided, the user can move on to the next step of the procedure. I made use of the approaches and the memory stick in order to characterise each function that was included within the data flow diagram. These strategies have all been gleaned from a variety of outside resources, and more especially, the internet. After that, will get some practice in by entering the information about bank account and the amount of money want to send so that may become proficient in the foundations of making a money transfer. This is taken care of by the Transfer procedure, which is in charge of executing the necessary debit and credit procedures in order to move money from the source account to the destination account. The Transfer procedure is responsible for handling this. I had a hard time not just developing the data flow diagram for the system but also the control flow diagram for the system, and during both of those processes, I was trying to figure out which system events were relevant. In the end, I went back over the system design criteria and started developing the logical architecture based on an internal vision of how the data would flow through the system. This helped me have a better understanding of what needed to be done.

The system's development shouldn't get underway until after exhaustive requirement analysis and problem specification have both been finished. In order to successfully achieve this goal, it is essential to compile streamlined descriptions of each process and sub-process that the system manages. Because of this, it is absolutely necessary to make use of the models and procedures that are associated with software engineering in order to explain and design the fundamental flow of software as well as the expected end of the process. This is because software engineering is associated with the development of computer programmes. Textual descriptions of the procedure are preferable to graphical ones because they allow for a more intuitive comprehension of the capabilities of the programme and the intended results of each operation. Graphical descriptions of the procedure are preferable because they are more time-consuming to create. One can search the internet and find graphical, great study, or pivot table descriptions of the technique. In addition to this, it directs them through the steps necessary to set up an RMT Framework that is fully functional within the new bank.

R education in the knowledge and abilities required to analyse and comprehend a real-time software programme even as it was being constructed was the primary purpose of this project. The process of reviewing real-time money transfer systems, for example, makes use of data flow diagrams and state diagrams. This helped to define the purpose of these diagrams, which was one of the objectives of the evaluation process. Because of this task, I was able to immediately put everything I had learned in my classes into practice. I found this to be an extremely beneficial experience. I've learnt a lot about control specification diagrams, including state transition diagrams and process activation tables, two of the many various types of diagrams that are.

References