Great Deal! Get Instant $10 FREE in Account on First Order + 10% Cashback on Every Order Order Now

1 CMP73010 Managing Software Development Assignment 1 2 CMP73010: Managing Software Development School of Business and Tourism Session 2, 2020 Assignment 1 This assignment is due on 24th August, 2020...

1 answer below »
1

CMP73010

Managing Software Development
Assignment 1







2
CMP73010: Managing Software Development
School of Business and Tourism
Session 2, 2020
Assignment 1
This assignment is due on 24th August, 2020 at 11:00 pm. The assignment has a component that must be
completed on-line but a majority is a written task. Suggestions for the report structure are given in each
section of the requirement. The report itself should be submitted through the Turnitin link in your MySCU
site. The maximum word count for the report is 1500 words (excluding headings, references, tables and
appendices). This assignment is worth 20% of your overall mark.
Please note that the assignment is due some weeks after the required materials are covered in the on-line
sessions. Please do not leave the assignment to the last minute as you can start work on much of the
assignment well before the due date. If you do require an extension for submission you must request this
efore the due date. Unless an extension is agreed, a late penalty will be applied. Each day late on submission
will apply a 5% mark deduction penalty. Please note that a timestamp of 11:01 on the due date is considered
one day late.
This assignment positions you as a software development consultant in a ‘big-4’ consulting firm (e.g.
Deloitte, EY, KPMG, PWC) and covers testing, configuration management and software tendering
assignments for different clients in your portfolio.
Important: You must submit your own solution with reasoning, however, we are perfectly happy for you
to chat and discuss with your classmates but ultimately you submission must be your work. The last bit is
particularly important. Do not copy and paste your classmates work and do not let your work be copied.
This can have serious ramifications for academic misconduct. What we are looking for is your unique
thought process behind your designs and solutions, as well as the actual solutions. Reports which do not
give satisfactory reasons for their designs and solutions will be penalised.
Part 1 – Testing (10 marks)
There are two components to this part of the assignment. You are
equired to produce an acceptance test description and a detailed black-
ox test description. These two test types are unrelated so you should
consider them separately. Note: testing tables are not counted as part of
the word count.
The Acceptance test (5 marks)
The consulting firm you work for has been contracted to develop a new
‘rideshare’ app (e.g. Uber, Ola). In particular, the client has asked your
team to specifically develop an acceptance test that focuses on user
privacy. The system user requirements for privacy in this test must
address:
1. The system provides a secure login and verification system
2. The system must provide a secure payment system
3. The system must verify the user enters the co
ect vehicle
4. The app does not collect user ‘location’ related information ‘by
default’
5. Third party services do not automatically obtain user information and that
the user should have the option to authorize third-party services if they wish
3
Outline an acceptance test for the above system as described by generating scenarios of each requirement.
In the study guide, this is steps 1, 2 and 3 of the acceptance test criteria. Most of step 1 is in the above
system description but you can refine and expand if you wish. These scenarios will not count to the total
word count. It is strongly suggested you do research on ride-sharing apps. Analysing comparative ride-
share will prompt your approach to generating the ‘scenarios’ for this test and place yourself in the
perspective of the user. You may even download an example of one (they are free to download and install),
ut it is not necessary.
Remember that acceptance tests can be designed without access to the actual product. Detailed testing of the
product is for the next part of this assignment (detailed black-box testing). You can enhance the
equirements above if you wish or clarify them based on your own knowledge. If you do adjust the
equirements your plan will be assessed against your new specification.
The detailed black-box test plan (5 marks)
As part of a client presentation to explain the benefit of black-box testing to both a technical and non-
technical audience, you are asked to design a detailed black-box test for a popular software product.
The product to develop the detailed black-box test plan is the PowerPoint 2016 Print dialog, as shown
elow. This version of Powerpoint is available to all students so you can see its operation if you need to.
The various drop-down lists will vary between users of the software. When you specify tests, you can
assume that the setup for the test can be achieved. For example, you may say “add five printers and select
the last one” and assume that this can be achieved.
Produce a detailed black-box test plan for this dialog box. You do not have to produce a detailed black-
ox test for any dialog box or new screen that any of the controls launch. However, you may have to refer
to the selectable options for testing each of the widgets on this dialog as you test the interaction between
widgets.
Note that you can, if you wish, apply your test plan to the product, e.g. you can test individual input fields
and interaction between fields. This is a commercial product, so you would expect the product to pass the
test (if you do find a bug then we will notify the software developers). For this assignment we are looking
at the test plan, not the actual test results.
For the detailed test plan you will be assessed based on how your test plan applies to this part of the total
product. The total PowerPoint 2016 product is an extensive system so do not attempt to do a
detailed test on more than this dialog. Remember that testing is a creative process, especially when
trying to
eak the software. You should come up with test ideas that other people will not think of (including
your marker). In addition, it will not be possible to exhaustively test the software. Marks will mainly be
awarded on the completeness of your strategy for testing for each widget. Creative testing ideas will be
sufficiently rewarded but there are basic testing strategies that you must describe.
4
Part 2 – Configuration management (5 marks)
Code/file version management (2 marks)
Version management systems are a daily reality for the software development professional. On GitHub is a
public project named: TeachBen/CMP73010-assignment1-2020
You are required to sign up to GitHub and then:
1. Fork this project into your public space (1 mark)
2. Modify the Word document called CMP73010.docx (it contains instructions) and request a pull
of the project (1 mark)
Note: at various times the project manager will pull changes into the mainline. This will be reflected in your
GitHub view of the project.
Important: In your assignment submission for the rest of the assignment you must state your
GitHub account name! (So that the marker can confirm your project activity). Remember that your name
will be public so please do not disclose any personal information. Do not place your student-ID in the
GitHub document or elsewhere in the project. As this only requires your GitHub account name it will not
e counted among the word count.
Build Management (3 marks)
A client of yours has confidential plans to develop an open-source web
owser and has asked you to provide
advice on build management by looking at a competitor (Mozilla ‘Firefox’).
Give your advice as follows:
1. A
ief description of the nightly build system of Mozilla Firefox
for managing changes to software and systems (1 mark)
2. How Mozilla a
ives at a release of Firefox that is distributed to
the public (1 mark)
3. Advantages and Disadvantages of this system for the client (1
mark).
Note that the nightly builds evolve over time so carefully reference the facts
that you have gathered and indicate the dates to which your descriptions refer.
You should be able to answer this section in about 400 words.
Part 3 – Request for Proposal (RFP) (5 marks)
Provide a detailed RFP for the following system of your client, Spearhead Technology Services.
Spearhead Technology Services is a business that sells a variety of Internet of Things (IoT)
products (e.g. IoT sensors, smart city devices such as; traffic lights and waste solutions,
smart home devices and appliances such as; smart entertainment systems, smart lighting
systems, smart refrigerators, smart toasters and more). They also provide IoT device
epairs and accessories. They want an integrated system to support their six
anch shops
as the opportunity arises. They envisage the system will evolve over time and plan to
expand to many more locations. Their initial requirements are:
1. Provide a customer relations database with information about products and services
purchased, devices left with them for repair (customer details, customer purchase history,
problem report, work details, etc.)
5
2. A marketing system that allows for digital marketing using e-mail, social media, and any other
modern marketing techniques. This will use details in the customer relations database but allow
other prospective customers details to be entered in an existing Spearhead Technology Services
website (not part of this RFP).
3. A stock management system that includes products for sale, parts for use in repairs, automatic
ordering from wholesalers. The system must be able to be used for individual locations to find
products and parts at other Spearhead Technology Services locations when necessary. As the
company specialises in IoT products the SMS will need to be able to have real-time monitoring
and diagnostics of some IoT products (e.g. smart cities products).
4. Provide
Answered Same Day Aug 19, 2021 CMP73010 Southern Cross University

Solution

Neha answered on Aug 22 2021
148 Votes
SOUTHERN CROSS UNIVERSITY
ASSIGNMENT COVER SHEET
For use with online submission of assignments
Please complete all of the following details and then make this sheet the first page of each file of your assignment – do not send it as a separate document.
Your assignments MUST be submitted as either Word documents, text documents with .rtf extension or as .pdf documents.    
    Student Name:
    
    Student ID No.:
    
    Unit Name:
    
    Unit Code:
    
    Tutor’s name:
    
    Assignment No.:
    Assignment 1
    Assignment Title:
    
    Due date:
    
    Date submitted:
    
Declaration:
I have read and understand the Rules Relating to Awards s18 as contained in the SCU Policy Li
ary. I understand the penalties that apply for plagiarism and agree to be bound by these rules. The work I am submitting electronically is entirely my own work.
    Signed:
(please type your name)
    
    Date:
    
End
Contents
Executive Summary    2
Part A: Testing    2
Introduction    2
Acceptance Test    2
Black Box Test    5
Conclusion    7
Part B: Configuration Management    7
Introduction    7
Code/File version Management    7
Nightly Build Management    8
Conclusion    8
Part C: Request for Proposal    9
Introduction    9
Spearhead Technology Services    9
Request for proposal timeline    10
Conclusion    11
References    11
Executive Summary
In this report we will discuss about the testing and request for proposal this report is divided into 3 parts. The parties are to perform the testing function over cool scenarios. It allowed us to learn about the acceptance testing and black box testing. The acceptance testing is performed over online ride application and black box testing is performed over the Microsoft presentation 2016. The Part B is to learn about the configuration management and the nightly build system for the project. In part C a case studies provided for an industry wants to create the request for proposal regarding their website.
Part A: Testing
Introduction
The testing is the most important part of the development of a system. When we start the development of a system all the requirements are mentioned in the document and testing helps us to make sure that all the requirements are fulfilled by the system. Testing is performed before sharing the system to the client. There are different types of testing but in this report, we will learn about the acceptance testing and black box testing.
Acceptance Test
In this case testing is performed over online riding application. The case study includes different scenarios for the testing. It informs that the user needs to login into the system to use the vehicle. The system will not store the location of the user without their permission and it will allow the user to select their right to for them. The system will try to make sure that the user has selected co
ect vehicle and the database about the weaker and user is well. Acceptance testing will be tested for the secure payment mode (Miller, R., & Collins, C. T.).
S1. The system provides a secure login and verification system
    Scenario
    Expected Outcome
    S1.1 User enters valid username and password
    System verifies the data from database and allows user to enter into the system.
    S1.2 User enter invalid username and password
    System restricts user to enter into the system and notifies same.
    S1.3 User enter invalid username or password.
    System restricts user to enter into the system and notifies the same.
    S1.4 User enters valid username but invalid password
    The system clearly informs the user about the invalid password.
S2. The system must provide a secure payment system
    Scenario
    Expected Outcome
    S2.1 User makes payment using the system
    The system allows the payment and keeps the data secure.
    S2.2 User enters invalid information
    The system denies the payment from the user.
    S2.3 User selects different card type and enters information for another one.
    The system informs the user about the invalid entries.
    S2.4 User enter all the details but cancels it before making the confirmation
    The system does not store any information about the payment and cancels the order.
S3. The system must verify the user enters the co
ect vehicle
    Scenario
    Expected Outcome
    S3.1 User enter valid vehicle...
SOLUTION.PDF

Answer To This Question Is Available To Download

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here