ISYS1001 Web Dev 1 Assignment 2
ISYS3001 Managing Software Development
Practical Skills
Copyright By PowCoder代写 加微信 powcoder
Task: GitHub, Builds and RFP
Unit Objectives: LO2, LO3
Due Date: Monday of Week 4, 11:59 pm
Weight: 40%
Must be completed as individuals.
Task Descriptions:
Code/file version management (8 marks)
On GitHub is a public project named: SCUteach/2022-Term1-Assignment1
You are required to sign up to GitHub and then:
1. Fork this project into your public space
2. Modify the Word document called ISYS3001.docx (it contains instructions) in your own repository and create a pull request to the main repository (4 marks)
Note: At various times the project manager (repository owner) will pull changes into the mainline. This will be reflected in your GitHub view of the project.
Important:
· You will need to add your GitHub account name to your assignment! (So that the marker can confirm your project activity).
· Remember that your name will be public, 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 be counted among the word count.
Build Management (12 marks)
A client of yours has confidential plans to develop an open-source web browser and has asked you to provide advice on build management by looking at a competitor (Mozilla ‘Firefox’).
Give your advice as follows:
1. A brief description of the nightly build system of Mozilla Firefox for managing changes to software and systems (4 marks)
2. How Mozilla arrives at a release of Firefox that is distributed to the public (4 marks)
3. Advantages and Disadvantages of this system for the client (4 marks).
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.
Request for Proposal (RFP) (20 marks)
Provide a detailed RFP for the following system.
Aussie Business Buzz (ABB) is a business that sells a variety of technology products (e.g., PCs, laptops, phones, routers), provides device repairs and mobile device accessories. They want an integrated system to support their 4 branch 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. 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.)
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 the existing Aussie Business Buzz 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 ABB locations when necessary.
4. Reports for management, who may be at any location, of the status of all the above so they can order stock, recruit staff, and make other management decisions.
Your RFP should use one or more guidelines that you will reference. You may be tempted to go overboard here so try to restrict your RFP to a reasonable size (up to 1000 words maximum), less if possible. Remember that the fewer restrictions the better in an RFP so that the responders can come up with new ideas that you have not imagined so far. This also means your RFP will not contain much technical information about the requested system but will contain information about your existing systems (the website unless you add to the specification).
Your RFP should allow for bespoke software development; but it should also clearly be able to consider existing applications, solutions built from components, SaaS solutions, other solutions, and any combination of these.
As you will learn, your RFP must contain:
1. The system description
2. Explanation of how you would evaluate proposals received
3. Explanation of how you would answer questions
4. Any other facts that would ensure proposals are useful to you and worth a supplier’s effort to respond to the RFP
Note there are many things missing from the above specification that you may wish to add to your RFP. A lot of your RFP will be details that you will need to make up, e.g., who to contact and how. You can use your own information or invent names and other data along the ABB theme.
Marking Criteria:
The rubric for this assignment is available on the MySCU site and will give the criteria for marking.
Getting Help:
This assignment, which is to be completed individually, is your chance to gain an understanding of the practical side of version management using GitHub, investigating and familiarizing yourself with system builds and writing a request for proposal. It is important that you master these concepts yourself.
Since you are mastering fundamental skills, you are permitted to work from the examples in the MySCU site or textbook, but you must acknowledge assistance from other textbooks or classmates. In particular, you must not use online material or help from others, as this would prevent you from mastering these concepts.
This diagram will help you understand where you can get help:
Encouraged Attribution Required
Not acceptable Ask tutor
Be aware if you do get help from one of the red sources, you are at risk of failing the assignment, or the unit.
Online Forums
Students outside unit
Hired coders
Classmates
Private Tutors
ISYS3001 Managing Software Development | Practical Skills 1
程序代写 CS代考 加微信: powcoder QQ: 1823890830 Email: powcoder@163.com