CMP73010 - Managing Software Development: Assignment 1 Report - 2019

This report, created for the CMP73010 Managing Software Development course, encompasses three key sections. Part 1 focuses on acceptance testing, detailing scenarios such as acceptable file formats, submission time display, word count notification, submission receipts, and draft submissions. Part 2 explores black box testing, providing a test plan for Microsoft Word 2016, and also includes a discussion on pull requests, outlining the advantages and disadvantages of daily builds. Part 3 presents a Request for Proposal (RFP) for Gold Technology, covering the company's introduction, ownership of deliverables, non-disclosure agreements, system descriptions, vendor responsibilities, and evaluation criteria. The report aims to provide a comprehensive overview of software development principles and practices, addressing various aspects of the software development life cycle, from testing methodologies to project management and vendor selection.

Running head: CMP73010 - MANAGING SOFTWARE DEVELOPMENT
CMP73010 - Managing Software Development
Name of the Student
Name of the University
Authors note

1CMP73010 - MANAGING SOFTWARE DEVELOPMENT
Part 1
Acceptance Testing
Scenario: The student wants to know what the acceptable formats that can be
submitted.
Acceptance criteria: The Acceptable format for different type of the assignments are
displayed such as different documents formats that includes (.odt, .doc, .docx, .pdf, .xlx).
For different other assignments such as .sql, .accdb, .html etc are displayed whenever
students try to upload any other file types that are accepted by the system.
Student submission time and dates: Student wants to know, the remaining time to
submit a specific assignment.
Acceptance criteria: The time is displayed in remaining hours and minutes from the
actual deadline for the assignment to submit.
The Time displayed must not be greater than actual deadline.
Notify Word-count
Scenario: Student wants to know the total word count in the submitted paper.
Acceptance criteria: The system should count all the words in the submitted file and display
the total count on the submission portal. If the required word count for an assignment is not
met then it will prompt an error displaying error message about the remaining word count for
the assignment.
Send a receipt of submission
Scenario: The student submits solution for an assignment to the system.

2CMP73010 - MANAGING SOFTWARE DEVELOPMENT
Acceptance criteria: The system should sent a mail to the registered mail id of the student
informing that the assignment is submitted to the system.
Draft submission of the assignment
Scenario: The student wants to check the draft solution with the professor.
Acceptance criteria: The system will have some specific button or container to which the
draft solution can be uploaded by the student for feedback from professor.
Upload of draft solution should not impact on the deadline displayed for the final and
complete solution.
Black box testing
As the black box testing is for the testing the functionality without having the in depth
knowledge of the internal logic. In this testing process specific knowledge about the code of
the developed application is not available to the tester. Consequently internal structure as
well as programming knowledge in general is not available. The tester of the application is
aware of the functionalities of the software needs to do but is not the way it completes the
functionalities.

3CMP73010 - MANAGING SOFTWARE DEVELOPMENT
For the word 2016 following is the test plan.
Test case Output
Add the document to Fax Completed Successfully
Send the print document command and print The Document can be printed using a
printer by selecting available printers
Layout of the page can be changed using
printer property.
Completed successfully through orientation
option.
Print a specific page of document or
complete document.
Both options can be completed successfully.
Determine the size the pages such as A4,
A3, Statement etc.
Page size changed.
Print one or multiple pages on every sheet
used in the
Selection 2, 3 or multiple pages can be
printed using the printer.
Change margin space for the document Margin changed in the document.

4CMP73010 - MANAGING SOFTWARE DEVELOPMENT
while printing.
Part 2
Pull request
Name of the Github Account is dpatel31
Advantages of daily build
Reducing the risk of Integration error
In any software development project scenario, one of the most important risks that a
development team can faces is numerous integration errors. At the time when the team
members of the development team integrates their codes with each other’s module on which

5CMP73010 - MANAGING SOFTWARE DEVELOPMENT
they were working separately it may happen that, the composite code after the integration
does not work as per the desired bench mark.
Depending on the time or period of the project at which the incompatibility is
identified debugging and resolving the issues can take longer span of time that may delay the
delivery of the software project. If the integration of the modules has been completed earlier,
the changes in the program interfaces, major changes in the system /redesigned can be
achieved earlier. In case of daily/nightly builds this issues can be easily addressed.
Easy error diagnosis
In the daily build process it is easy to diagnose defects in the developed project. As
the desired software product is built/developed and tested every day, it becomes easier to
pinpoint the time or stage at which the product is broken. If the developed product worked
correctly at given day and is broken on the next day’s build then the code segment added in
the next day can corrected easily instead of searching the complete code of the software
project that takes a lot of time.
Perfects the Build Process - The development team that builds after a complete
coding cycle that sometimes takes 6 months’ time depend on a fragile build process for the
desired project that requires too many tweaks to get the right build. By using daily builds, it
is possible radically reduce the time period consumed for development to quality assurance
process.
Disadvantages of Daily Build
In case the development architecture includes legacy systems or servers then it
becomes complex in order to support continuous delivery of the daily build solutions without
significant amount rework on the developed modules.

6CMP73010 - MANAGING SOFTWARE DEVELOPMENT
In the daily build scenario, it is very important to develop and utilize suitable test
procedures in order to ensure the quality.
This build process may incur waiting time as there may be multiple developers who
are trying to integrate their developed code at the same point of time.
Part 3
RFP for Gold Technology
Introduction
As the nature of the business of Gold Technology is sales and repairing of the PCs,
laptops, phones, routers and it has determined to have a system that will help in the different
operations at all the 6 branches whenever there are opportunities.
Ownership of Deliverables
The custom software developed for under this project will be the sole ownership and
property of Gold Technology.
Non-Disclosure of Confidential Information
Unauthorised release of sensitive information about the any kind of operation,
including but not limited to data, identifiable information of the staffs, customers of the Gold
Technology, database structures used for the developed application or existing system is
included in the Non-Disclosure Agreement between Gold Technology and Vendor
developing the system and governing the information provided by the organization.

7CMP73010 - MANAGING SOFTWARE DEVELOPMENT
System description
The intended system should be developed using a client server architecture on the
cloud platform so that there is a centralized database or repository of the available products
and spare parts for sales and repairing. The system must include a module with database
connectivity for the customer relationship management that will help in CRUD (Create,
Read, Delete and Update) operations about the products/ services purchased by specific
customers, devices and its details that needs to be repaired, different customer details such as
customer name, address, phone, email, purchase history, problems reported as well as
completed work details.
Another module that needs to be included in the system is marketing module that will
be helpful in carrying out marketing campaigns through the use of the existing customer
database by e-mail newsletters, social media along with the modern marketing policies.
Along with this the use of the customer database as well as other potential customers details.
In addition to that, the system will include the stock management module. This
module will help the staff at the branches to track the sock level of the products for sale,
stock level of the parts for use in repairs. In addition to that, there must be automatic ordering
functionality that will be triggered for a certain reorder level to get the product or parts from
wholesalers. Moreover, this module needs to provide consistent data about the products to the
individual users working at any of the six locations so that they can find products and parts at
other Gold Technology branches to meet the need at a given point of time (if the specific
branch lacks a product or repair part).

8CMP73010 - MANAGING SOFTWARE DEVELOPMENT
Resources to Be Provided by the Vendor
The vendor will be responsible for providing the End to End Testing Environment in
order to continue over the lifetime of the custom developed software usage at Gold
Technology.
Training Environment and Training Program to the users in order to support the staff
to get used to the developed application.
Evaluation of proposals received
The proposal allows the organization for testing all aspects and functionalities of the
implemented software. This tests includes third party software integrations.
Software licenses used in the project required to be supported by Vendor Product
Testing. This includes but not limited to the use of the Licenses of Database Server, Third
Party Software Licenses which are used in the application.
User guides/Software manuals which outlines use system features along with the
custom features.
In addition to that above mentioned factors the proposals will be evaluated upon
Features and functionality of the system. Depending upon the necessary capabilities of the
proposed system and the functionalities simply be nice to have. Implementation time is
another factor.
Conclusion
The Proposals should clearly describe the implantation, cost, ownership terms, and
other necessary details for this software development project. As the organization quickly
requires to have the software solution up and running. If for some specific functionality it is
required to invest more time to get the right solution then this needs to discuss with the
organization.

9CMP73010 - MANAGING SOFTWARE DEVELOPMENT