Agenda For Nexus Distribution App Development

Case study: Nexus Distribution

This document extends the instruction on the course website. Read the instructions on the course website in addition to this document.

This assessment consists of

• A case study that requires you to apply your learning from the systems planning module.
• An ethical analysis which requires you to apply one of the readings provided on the course website.
• A conceptual development section that requires you to consider how systems planning tasks impact on a systems development project.
• A peer review/learning reflection section; students who are working in teams are to answer the peer review questions; students working independently are to answer the learning reflection questions.

The feedback sheet lists the assessment criteria. Look for it on the assessment’s webpage. Take note of which sections carry the most marks.

Note that this document’s word count is 3650 without any answers, so

• Don’t worry if the final word count seems high.
• Also, there are some diagrams in this assessment so don’t worry if the final word count seems low.

Draw the diagrams by hand, photograph, and insert the photographs in this file. If you prefer, you can use Word’s drawing tools (or some other drawing or modelling software) but you may find working with pen and paper is faster, easier to amend, less cumbersome, and more reliable with respect to layout.

When referring to the exemplars on the course website, read the old assessment specifications carefully because the assessments differ every study period.

In the previous study period, teams spent an average of 41 hours on this assessment.

• Pace your team accordingly.
• For best results
  • Do not attempt to complete the whole assessment in one session.
  • Work slowly and carefully.

In addition to the instructions on the course website

• Do not overlook the ‘Why?’ questions.
• Read the case study carefully.
• Keep track of the hours you spend.

Make assumptions where necessary. Scope for assumptions has been deliberately included in this assessment because it is often necessary to make assumptions openly when dealing with a client who is under-informed with respect to information systems. Label assumptions clearly. Here’s an example from a previous study period,

Assumption: As the passengers of Titanic II may be from any nation, we have assumed a currency converter is required for the ticket-purchasing function. 

Nexus Distribution is a small film distribution agency that focuses on limited release art-house films. It has been in business for a decade and has an existing information system for administering its business processes. Joy Moody started Nexus with her long-time professional contact Deane Jackson. Joy has a leadership and marketing role and Deane manages operations. Louise Taylor and Elizabeth Page are spotters who attend film festivals (eg Sundance, Cannes, Sydney, Toronto, London, etc), identifying films that align with the Nexus Distribution focus, bidding for, and often signing, those films. This team of four work closely to sign 15-20 films each year, optimising the distribution of each film so that returns for Nexus and for their clients (the film-makers and the theatres) are maximised.

The existing information system consists of three databases.

• Catalogue
• DistributionNetwork
• Travel

Louise and Elizabeth do most of their work while travelling and they communicate with Deane via email, text messaging and phone calls. Louise and Elizabeth attend only the largest film festivals together; usually they work independently of each other. When they are at a film festival, they work highly irregular hours and, in addition to the tasks outlined above, their work includes socialising with, and occasionally entertaining, potential and existing clients. Clients are entertained when the film they have made is of such high quality that more than one distribution agency is competing for its distribution rights. In these cases, Elizabeth and Louise take the clients out for dinner or to a bar in order to build robust working relationships and to create an opportunity for uninterrupted discussion of why and how the client’s interests are best served by Nexus. Louise and Elizabeth are consummate networkers; they are confident, good-humoured and charming in all social circumstances, building relationships with and between people working at all levels of the international art-house film industry.

Current Information System and Communication Issues

However, the communication practices between Nexus staff are not up to date and this has led to inefficiencies and wastage of Louise and Elizabeth’s talents and efforts. As their time at film festivals is expensive (flights, accommodation, registration fees, entertainment costs, etc) it is desirable that their time is not wasted. For example, a new film may be shown at several film festivals simultaneously; if Elizabeth has already seen it at Toronto and passed on it (or bid for it and signed it), when Louise is at the Venice film festival, she does not need to waste her time viewing that film and can focus on other films. There are many other instances in which their communication practices fail to optimise the (mostly asynchronous) day-to-day collaborations between Louise, Elizabeth and Deane.

While Louise and Elizabeth work on building Nexus’s catalogue, Deane builds its distribution network (in addition to his significant administrative role). This entails signing various distribution service providers (both independent and chain) to the Nexus distribution network. A distribution service provider might be a VOD (Video on Demand) provider, a chain of theatres, an independent theatre, etc. Deane spends about half of his recruitment effort approaching providers that do not already screen art-house films. The other half is spent on providers which already adopt an art-house focus. While it is a key facet of the Nexus business model, building the distribution network does not consume anywhere near as much effort, money and time as spotting films. Deane estimates that for every dollar spent on building the distribution network, a hundred are spent on spotting films.

Deane is directly responsible for accounting, travel arrangements and reporting. Also, he is indirectly responsible for contracts, which he outsources to a legal firm specialising in contracts for this type of work.

Joy’s role is largely centred on vision and leadership. However, prior to starting Nexus she built a reputation in film marketing and her practical skills in this area are an essential ingredient in Nexus’s success. Every time a new film is signed to Nexus, Joy, Deane, Louise, Elizabeth and the film-makers have a four hour meeting. Occasionally, these meetings are in person, but more often they are held online. These meetings can be hard to schedule because participants are very busy and in different time zones.

During these meetings, in order to design the film’s marketing strategy, they leverage Louise or Elizabeth’s observations of the film, Deane’s knowledge of the Nexus distribution network, Joy’s marketing expertise and the client’s vision. A marketing strategy includes artistic vision, media, release windows and release schedule.

Client Needs and Requirements for App Development

Artistic vision is primarily driven by the client and Joy with input from Louise or Elizabeth. It is actioned by Deane, who reviews the artists who have worked with Nexus in the past, considers the artistic vision, and prioritises the artists according to how well their unique talent, reliability and experience match up with the marketing strategy’s artistic vision. After the meeting, Deane approaches the artists one by one to discuss their availability and to eventually establish a contract.

Media (film, video, television, DVD, VOD, etc) is negotiated between Joy, whose mission is to optimise returns, and the film-maker, whose mission is exposure. With input from Louise and Elizabeth, who have viewed more films than anyone else in the meeting and who therefore have the most comprehensive view of the international market, a binding consensus is reached and documented.

Joy and Deane, who aim to maximise the size of the audience, are largely responsible for determining release windows and schedule, however the client’s needs are taken into consideration. This is achieved by application of market intelligence and expertise. In most cases, a film is screened in theatres on a schedule that will maximise the audience (eg avoidance of major cultural events, avoidance of similar films, knowledge of forthcoming films, etc). Also, films are screened in theatres (primary distribution service providers) prior to being released via secondary distribution service providers (eg VOD service providers, DVD runs, etc). The duration for which the film is screened in theatres depends upon various factors (audience, the film’s performance in other markets, the agreement between Nexus and the film-makers, the agreement between Nexus and the theatres, etc). For most films, the theatrical release date is preceded by four weeks of postering and trailers, wherever possible working with the film-makers in order to leverage the social profiles of those who worked on the film (eg the actors and crew). For highly anticipated films, these four weeks may extend to six or eight and may require Deane to schedule interviews for the film-makers or actors with local media.

Although the existing IS meets Nexus’s administrative needs, the ongoing daily communication problems and the difficulties of scheduling and running online meetings need to be addressed. Deane thinks Nexus needs its own app so that database updates can be done by anyone at any time and he has contacted your workplace, IT Foundry, to enquire further. You have been allocated the task of systems planning for the development of an app for Nexus.

Proposed Solutions for the App Development

Also, although they are very talented, experienced and respected in their fields, the entire Nexus team are inexperienced in systems analysis and design. They are confident you will come up with relevant ideas, they anticipate your suggestions and they expect you to catalyse and drive all technical aspects of the project. These clients are very much open to suggestion. 

The preliminary investigation you wrote up for the Nexus project enabled you to develop a basic understanding of the business context. Your scope lists captured the project’s key elements and made a positive impression on Joy, Deane, Louise and Elizabeth. They have approved the project’s progression to system analysis and you have scheduled a meeting with them.

Recall: you can make assumptions in this assignment (as noted in the instructions above). Also, you can use the course forum if you have any questions.

1. Prepare for this meeting. Write an agenda that includes six topics you would like to discuss with them (if you do not know what an agenda is, look it up on the internet). These topics should be derived from your planning documents and should enable your clients to talk about the things you need to know during systems analysis (eg, the data and how it is processed).

• Agenda 1 – Identification of requirements and analysis
• Agenda 2 – Discussion and identification of the organizational structure in Nexus Distribution
• Agenda 3 – Determination and analysis of requirements
• Agenda 4 – Discussion with designs and screenshots of interfaces for the system
• Agenda 5 – Identification of system alternatives and determining one for development
• Agenda 6 – Discussion on system diagrams and approval from client.

After this meeting, the following requirements are known:

• Louise and Elizabeth must be able to enter data into the Catalogue database from their smartphones
• Louise and Elizabeth must be able to query the Catalogue database with their smartphones
  • For example, when they are planning their viewing schedule Louise and Elizabeth need to be able to check whether a film has already been viewed and signed (or passed on)
• Dean must be able to enter, access and amend data in the Travel and DistributionNetwork databases from his smartphone and from his desktop computer
• Louise and Elizabeth must be able to view future travel itineraries and hotel bookings on their smartphones
• Louise and Elizabeth must be able to enter, access and amend information on their relationships with clients or contacts from their smartphones
  • For example, a new client or contact’s name; if they are a filmmaker (a director or a producer), which film and how were they involved with that film; if they’re not a filmmaker, what their business is and why the relationship is important to Nexus; whether the client or contact was made by Louise or Elizabeth; when and where the client or contact was made; their entertainment preferences; etc
  • A new database will be needed for this relationship data
• Joy must be able to view summaries of recent business activity from her smartphone and from her desktop computer
• Joy wants to be able to tailor these summaries on an ad hoc basis
  • Examples include recently established client relationships; recently signed films; Louise or Elizabeth’s notes on the recently signed films; recently planned travel; an annual overview of the film festivals attended by Louise and Elizabeth; when and where these festivals are held, etc.
• The whole team must be able to schedule and conduct meetings on smartphones (Joy, Deane, Louise and Elizabeth) and desktop computers (Joy and Deane)
  • Scheduling must account for Louise and Elizabeth’s travel itineraries and for whichever time zone they will be in at the time and date of the meeting
  • No one from Nexus will be involved in scheduling – the system will automatically find the four best dates and times
    • These dates and times will be sent to the client (their contact details will be in the new relationship database or, if necessary, the app will alert Deane and he will look up the contact details in his paper file, enter the details and, accordingly, the app will update the relationship database)
    • The client will choose which of the four dates and times is best for them
    • The app will make the booking, alert all participants, update their calendars and, on the day, provide an alert 15 minutes before the meeting starts
  • It must be possible for a client to call in to these meetings (Skype, phone, any other method)
  • Meetings must be voice recorded for future reference
  • A new database will be needed for the meetings data

You make a start on systems analysis. You realise more detailed information will come to light over time, which may require you to amend your current analysis.

Recall: you can make assumptions in this assignment (as noted in the instructions above). Also, you can use the course forum if you have any questions.

1. What is the purpose of data flow diagrams?

DFD (Data Flow Diagram) is considered as the graphical representation of functions, processes that helps in capturing, manipulating, storing and distribution of data. Data is distributed between system along with its environment and components of the system. DFD provides visual representation of the data flow and it acts a good tool for facilitating communication between a user and system designer. DFD structure allows to start from a broad overview and expanding it into various detailed diagrams for development of a system.

1. Do data flow diagrams show system logic and decision points? Explain.

DFD presents the relationship between the various components associated with a system or program. DFD shows the system logic and decision points as it relates to the system modelling in a high level detail that shows the transformation of input data into output results. The transformation occurs through sequential functional transformations. The transformation of input data is carried out by considering the logical and decision points.

1. Why is it important for a systems analyst to understand how data flows through an information system?

A system analyst must be able to understand the data flows through an information system to determine the logical model that is being followed the system. The data flows present “what” is being done by the system and “how” it is done. Hence, it is important for a system analyst to understand the data flows so that they can determine capability of the system and make logical decisions to analyse performance of the system.

1. Draw a context diagram for the Nexus information system.
2. Draw a Level 0 DFD for the Nexus information system.
3. With respect to DFDs, what does ‘balanced’ mean?

Implementation Plan and Timeline

The term “balanced” in context to DFDs means that all the incoming and outgoing flow from a process described in the parent diagram are preserved while decomposing it into next level. The concept of balancing in DFDs is required for checking internal consistency of the system which is considered to be essential as various users with different expertise level may be involved within a project.

1. Draw two Level 1 DFDs for the Nexus information system.
2. Write a brief ‘how to’ guide (100-200 words) to help the Nexus team understand your DFD diagrams.

The DFDs present the information about the storage and distribution with a visual presentation so that it can be easily understood by the Nexus Team. The information system is place as the core element in the DFD from which the data flow occurs whenever, process is requested or initiated by users of the information system. The data storage elements in the DFD presents the defined storage for storing the data being transformed from input to output. Further the notations being used in the DFDs are described as below:

External Entity: This element represents a human, system or subsystem. It is considered as the source from where data is incoming our outgoing within a system. 

Process: This element is considered as the function or business activity through which there is occurrence of data manipulation or transformation. 

Data Store: This element is the medium for storing data that is produced or required by the process being carried out in the system. 

Data Flow: This element represents the information flow and the direction is depicted by an arrow to reflect upon from where the data is incoming and outgoing within the system. 

1. List the data stores and data elements in your DFDs, showing the data elements for each data store.

Data Store	Data Elements
Film and Travel
Film catalogue	Film information and Film Festival
Media record	Type of Media (film, video, television, DVD, VOD, etc)
Flight and accommodation	Flight and accommodation costs
Registration and entertainment	Registration fees and Entertainment costs
Distribution Network and Accounts summary
Service provider	Type (VOD (Video on Demand) provider, a chain of theatres, an independent theatre, etc.)
Expenses file	Total costs for travelling
Accounts statement	Total expenses for month or particular visit

Draw a FDD for the Nexus information system.

Identify and name four of the functional primitives in the Nexus information system.

The four of the functional primitives as identified in context to the Nexus information system are presented as below:

1. Prepare Film catalogue
2. Prepare Travel expense
3. Prepare Distribution Network
4. Prepare expense report and accounts statement

1. Draw a modular design for two of the functional primitives named in your previous answer.
2. Write a Structured English description for each of the other two functional primitives.

Prepare Film catalogue 

RECEIVE Film information request

GET Film information from Film catalogue file

CHECK entry record for film

IF Found = True

THEN Return “Information already entered”

ELSE Update record in Film catalogue file

SEND Updated record to media file

Prepare Distribution Network

RECEIVE Distribution network information request

VALIDATE information

CHECK entry record in Service provider file

IF Found = True

THEN Return “Service provider already exists”

ELSE Update new information in service provider file

SEND updated record to Distribution Network Summary

1. For which components of the Nexus information system will you recommend prototyping? Why?

The components of the Nexus information system for which prototyping is recommended are presented as below:

Preparing film catalogue: This component has to be included for the prototype such that the users (Louise and Elizabeth) will be able to easily keep record or the films or film festivals that they visit. They often travel differently to visit film festivals so there is a need for prototyping such that they will be able to store information of films remotely.

Storage of expenses and preparation of accounts statement: This component is required to keep track of the expenses being incurred upon the company while Louise and Elizabeth visits the Film festivals to gather information about films.

Preparation of Distribution Network: This component is required for Joy so that various service providers can gain access to the system and register with Nexus. Joy is responsible for developing the Distribution network so this component will help him to perform the required business operations.

Note that UML will be assessed in detail in the exam.

1. Explain how you will make the build or buy decisions for the Nexus information system.

The decision for build or buy can be made by determining the required modules for the new information system. The decision to build or buy depends on the requirements that have to be fulfilled by the system. The decisions are based on various criteria such as feasibility, cost and maintenance required for the system.

The decisions for building the proposed information system for Nexus or buying it depends on the feasibility of system means whether it will be able to cater the needs of the client along with determining suitability of the hardware or software required to run the system. Further, another criteria that has to be taken into consideration is the cost associated with hardware or software required to build the information system or buy the system. Finally, maintenance is also an essential factor while making such decision to build or buy the information system for Nexus. If the system will be built maintenance have to be carried in-house and if it is purchased from other sources then the maintenance will be done by them only which may lead to information security risk.

1. Your team has been asked to give a 30-minute presentation to Joy, Deane and your manager at IT Foundry, using a PowerPoint presentation. How many slides will you include and what are their titles?

From the analysis on identification of requirements, it has been identified that there will be almost 20 slides for presentation. The title for slides that will be involved in the presentation are presented as below:

1. Background
2. Problem statement
3. Requirement analysis
4. Meeting agendas
5. Purpose of Data Flow diagrams
6. Discussion on data flow with Data flow diagrams
7. Discussion on data flow with Data flow diagrams (continued)
8. Discussion on data flow with Data flow diagrams (continued)
9. Discussion on data flow with Data flow diagrams (continued)
10. Guide to help the Nexus team in understanding the DFD diagrams
11. List of data stores and elements
12. FDD (Functional Decomposition Diagram) for the Nexus information system
13. Identification of four functional primitives in the Nexus information system
14. Functional primitives (continued)
15. Modular design for two functional primitives
16. Structured English description for two functional primitives
17. Recommendations for prototyping
18. Decision making for build or buy
19. End Notes
20. Thanking slide 

Through your work analysing Nexus’s data requirements, you become aware of some unusual entertainment expenses on Elizabeth’s account. While she may have incurred these expenses legitimately, there are no similar transactions in Louise’s account. You are fully aware that Elizabeth and Louise regularly entertain potential clients and you are aware that this is an important method of developing clientele and industry knowledge. You are also aware that Elizabeth and Louise drive the Nexus business processes, creating business opportunities and building good-will for Nexus. However, these transactions are unusual and, according to your personal moral points of reference, sensitive. You are undecided as to whether you should inform anyone, and if so, who.

Analyse this scenario by responding the following questions. These questions encourage you to apply the stages of the ethical decision-making process described in Reynolds (2015). This reading can be located on the course web site. Do not overlook the ‘Why?’ questions as these support the development of your certitude.

1. Make a list of the facts relevant to the ethical problem.

The list of facts that are relevant to the ethical problem are presented as below:

• Unusual transactions in the account of Elizabeth
• Should the issue be informed
• To whom the issue have to be informed 

1. List the stakeholders and their positions.

The stakeholders that are associated with the presented ethical analysis case are presented as below:

Stakeholder	Position
Louise Taylor	Spotter
Elizabeth Page	Spotter

You have not yet made a decision. However, a decision is forthcoming. When the decision is made, what will its consequences be?

If a decision is made to inform the issue with transaction in account of Elizabeth then it may lead to termination of the contract as well as loss in reputation of Elizabeth.

If the decision is made to not inform about this ethical issue, may lead to further major risks with costs being bared by the company for travelling and entertainment. Joy as the owner may feel that entertainment costs will not be bared by the company.

1. Consider virtue ethics, utilitarianism, fairness, and the common good. When used correctly, these philosophical theories may lead your decision in a different direction.
   1. What does a virtue ethics framework tell you about the ethical problem?

From the perspective of virtue ethics framework, the ethical problem being identified is a major problem as it is against moral values of the company and it has to be analysed in detailed manner.

1. What does utilitarianism tell you about the ethical problem?

Utilitarianism tells that the problem has to be handled with efficient care and considering the moral values of human being such that the decision made does not hurts the associated people.

1. What does fairness tell you about the ethical problem?

Fairness tells that the problem is a major issue as the company can only sustain if there is clarity and clear information on the tasks being carried out by the employees.

1. What does the common good tell you about the ethical problem?

Common good tells that the problem have to be resolved by taking efficient steps so that those does not affect the moral values.

1. Identify and describe three different responses to the ethical problem.

The three different responses to the ethical problem are listed as below:

It should not be informed: This response means the issue will not be conveyed to anyone and the problem will continue to exist.

It should be informed: This response means that issue will be conveyed to owner or other person so that it can resolved by taking appropriate measures.

It should be handled personally: This response refers that the issue will be conveyed only to the problem owner so that she becomes aware and takes appropriate measures.

1. Which response is the best and why?

In context, to determined responses the third response is best as it will not disturb moral values of the individual as well as the company.

1. Refer to the stakeholders. How does the best response impact on the stakeholders?

The best response will help the stakeholders to become aware of their mistakes that should not be done in future and it will give a chance to rectify themselves in case there is any further discrepancy.

So far, this assignment has supported the development of skills required in professional practice, including ethics. Now, it supports the development of professional expertise.

Consider the Nexus case study and the systems analysis your team has completed. You may have completed the analysis with a lot of care. If so, your analysis is more likely to be effective in supporting future project activities.

Consider a situation in which the analysis was conducted in a careless manner.

1. What is the overall purpose of the systems analysis phase of a project and how does it differ from the systems planning phase?

The overall purpose of systems analysis phase is to determine the requirements that have to be fulfilled by the system whereas system planning phase means determining the steps that will be taken to develop the required system.

1. With respect to the systems analysis taskscompleted above, identify problems that may arise for the following stakeholders. Your answer should have six unique problems (two per stakeholder).
   1. Nexus

• Description of requirements: Different employees of Nexus may present different view or opinions on the requirements hence it may lead to improper identification of requirements.
• Changes in scope: During the design or development phase for the system, different employees may think that the design is not suitable according to their requirement due to which, there may be need for changes. This may lead to changes in design thus leading to changes in scope.
  1. Nexus’s customers or the wider community
• Understanding the system functionalities: The customers may not be able to fully understand the functionalities of the system means how to operate the system or how the system will provide desired outcomes according to their requirement.
• Accessing the system: The customers or wider community may face difficulty in accessing the system as they have to become a member of Nexus by registering themselves with personal information. The system will then generate a unique username and password for each user then only they will be able to access the system with their login credentials.
  1. Your own future work tasks (systems design tasks)
• Determining the system modules: The system will consist of different modules to cater the needs of different stakeholders. Hence, determining proper modules for the system is a complex task as every requirement has to be checked in detailed manner.
• Testing of the modules: Testing plays an important role in development of any information system so there is a requirement to identify and determine the suitable testing methods. If proper testing is not done then it may lead to failure of the system.

1. With reference to any three of the problems you have identified above, what are your conclusions about the importance of attention to detail with respect to systems analysis?

From the identification of problems, it can be said that there is importance of attention to detail with respect to systems analysis. The improper determining of the requirements may lead to required changes in the system module which in turn would incur high costs and time thus resulting into delay or failure of information system development project.

Recall the systems planning assessment asked you to draw some conclusions about the importance of attention to detail during systems planning activities. In this assignment, you are thinking about and demonstrating systems analysis.

1. Read and think about your answer to question 21 of the Systems Planning assessment. Compare it to your answer to question 27 Identify and discuss two important differences in your answers. Note: this question does not ask you to compare systems planning and systems analysis. Instead, it asks you to compare what you think about these two topics.

In question 21, the discussions are carried out on ethical decision making and moral values whereas question 27, relates to the importance of paying attention to detail. However, both the questions have an interrelationship between them as they have link with decision making if proper decisions are not made then the project may be delayed or even failure. 

Everyone in your team must visit SparkPLUS and review their teammates. When reviewing one of your peers, tell them three things they did well and three things they can improve.

NOTE: the systems design assessment will ask students to consider their weaknesses and strengths. If you do not tell them weaknesses and strengths, they will get lower grades in this future assessment.

Warning: If one person skips the peer review, the whole team will receive a lower grade.

Think about the tasks you completed in this assignment and reflect upon any knowledge you have gained from completing these tasks. Consider the UniSA Graduate Qualities.

1. Name two learning outcomes.

Note: although the Course Objectives on the Course Outline can be informative, please consider your personal learning experience. As you have a unique history, you will have unique learning outcomes; that is, someone who knew a lot about defining a project’s scope before starting this course cannot identify it as a learning outcome from this assignment; they will identify some other learning outcome. Also, do not repeat the learning outcomes from your systems planning assessment.

• Detailing requirements for client and system development
• Tools and techniques required for designing activities

1. For each of your learning outcomes, name one relevant UniSA Graduate Quality.

Example: “As noted above, my first learning outcome is _____________. This learning outcome correlates to _____________. My second learning outcome is _____________. This learning outcomes correlates to _____________.”

As noted above, my first learning outcome is detailing requirements for client and system development. This learning outcome correlates to determining the requirements of the client that have to be fulfilled by the system. My second learning outcome is tools and techniques required for designing activities. This learning outcomes correlates to identification of required tool and techniques that have to be used for designing diagrams to develop the system.

1. In your previous answer, you correlated two learning outcomes to two Graduate Qualities. Focusing on these two Graduate Qualities, and addressing each one separately, explain how this assignment’s tasks enabled you to further develop these qualities.

Detailing requirements for client and system development: This assignment tasks helped to improve the qualities as the assignment was based on a case study from which the requirements were to be identified. The processes required for requirements analysis were identified from this assignment tasks.  

Tools and techniques required for designing activities: The tasks in this assignment consisted of developing various diagrams to identify functionalities of the system. The diagrams were designed by identifying suitable tool that is MS Visio.

How many hours did your team invest in this assessment? This information will be provided to future students in this course.

Our team invested almost 45 hours in this assessment.

Thank you for your time and effort. I look forward to reading the submission. 

References

Abrahamsson, P, Salo, O, Ronkainen, J & Warsta, J 2017, Agile software development methods: Review and analysis. arXiv preprint arXiv:1709.08439.

Adams, K.M 2015, Non-functional requirements in systems analysis and design (Vol. 28). Heidelberg: Springer.

Ameller, D, Franch, X, Gómez, C, Araujo, J, Svensson, R.B, Biffl, S, Cabot, J, Cortellessa, V, Daneva, M, Fernández, D.M & Moreira, A 2015, August. Handling non-functional requirements in model-driven development: an ongoing industrial survey. In Requirements Engineering Conference (RE), 2015 IEEE 23rd International (pp. 208-213). IEEE.

Chitchyan, R, Rashid, A, Sawyer, P, Garcia, A, Alarcon, M.P, Bakker, J, Tekinerdogan, B, Clarke, S & Jackson, A 2015, Survey of aspect-oriented analysis and design approaches.

Dennis, A, Wixom, B.H. & Tegarden, D, 2015, Systems analysis and design: An object-oriented approach with UML. John wiley & sons.

Dick, J, Hull, E & Jackson, K 2017, Requirements engineering. Springer.

Eckhardt, J, Fernández, D.M & Vogelsang, A 2015, October. How to specify non-functional requirements to support seamless modeling? A study design and preliminary results. In Empirical Software Engineering and Measurement (ESEM), 2015 ACM/IEEE International Symposium on (pp. 1-4). IEEE.

Eckhardt, J, Vogelsang, A & Fernández, D.M 2016, May. Are” Non-functional” Requirements really Non-functional? An Investigation of Non-functional Requirements in Practice. In Software Engineering (ICSE), 2016 IEEE/ACM 38th International Conference on (pp. 832-842). IEEE.

Garfield, J 2017. Assessing Theoretical Concepts in Systems Analysis and Design: A Scaffolded Case Study Approach.

Khan, F, Jan, S.R, Tahir, M, Khan, S & Ullah, F, 2016, Survey: Dealing Non-Functional Requirements at Architecture Level. VFAST Transactions on Software Engineering, 9(2), pp.7-13.

Laplante, P.A 2017, Requirements engineering for software and systems. Auerbach Publications.

Mairiza, D, Zowghi, D & Gervasi, V 2014, Utilizing topsis: A multi criteria decision analysis technique for non-functional requirements conflicts. In Requirements Engineering (pp. 31-44). Springer, Berlin, Heidelberg.

Mylopoulos, J, Kolp, M & Giorgini, P 2017, Agent-Oriented Information Systems Analysis and Design: Why and How. In Systems Analysis and Design: Techniques, Methodologies, Approaches, and Architecture (pp. 111-131). Routledge.

Neto, P.A.S, Vargas-Solar, G, da Costa, U.S and Musicante, M.A 2016, Designing service-based applications in the presence of non-functional properties: A mapping study. Information and Software Technology, 69, pp.84-105.

Niu, N, Da Xu, L, Cheng, J.R.C & Niu, Z 2014, Analysis of architecturally significant requirements for enterprise systems. IEEE Systems Journal, 8(3), pp.850-857.

Reynolds, GW 2015, ‘An overview of ethics’, in Ethics in Information Technology (3^rd edn), Cengage Learning, Boston, pp. 1-39.

Tilley, S & Rosenblatt, H 2017, Systems Analysis and Design, 11^th edition, Cengage Learning.

Valacich, J, George, J & Hoffer, J, 2014, Essentials of systems analysis and design. Prentice Hall Press.