Reference no: EM133012269

SEP401 Software Engineering Principles

Assessment - Proposal

Context

A software engineering proposal is a document that a software developer submits to a business stakeholder for acceptance. A software project proposal describes what you are going to do, how you're going to do it, and what the results of that process will be. Your proposal should also show the benefits, funding and resources required before your get the approval from your stakeholders. In software development, the project does not exist until it has been proposed and given the approval. The project proposal is your first step at coordinating all the elements of your potential project. This is your first step in managing all the tasks, equipment and other materials you'll need and align them with a feasible schedule to achieve the project's objective.

This assessment will develop your ability to identify a problem, propose how you want to solve it and communicate these ideas to different stakeholders.

All assessments for SEP104 are integrated to help you develop your skills in producing high quality software solutions from the initial software engineering process to delivery. Your project proposal will provide the goals, objectives and structure of what the project looks like to help you focus when identifying and describing requirements for the other assessments. When making design and implementation decisions, you always look at the project proposal to help set the direction of your decisions.

The proposal you create for this first assessment, once approved, will be used for your requirements document that you will deliver in Part B of this assessment. Assessment 2 requires you to develop the Software Design Document and to include any feedback you receive from Part A & B of Assessment 1. Your Software Design Document that you produced in Assessment 2 should be used as the foundation of the Software Application you are asked to develop in Assessment 3.

Instructions

This assessment requires you to write and submit a Software project proposal.

Keep in mind that this is a proposal and that your facilitator has to approve it. Modifications and changes to the proposal might be required. The key is to diagnose the problem and propose a solution to convince the customer (reader) to accept your proposal. In this course, you are not required to come up with an innovative solution to an existing problem or a unique problem to solve. Some key steps to help you find a project topic:

• Identify a problem you want to solve (e.g, it takes too long to order food in a restaurant, patient records are still entered manually for some GP clinics, or board games should be accessible using other media)
• Think of possible solutions to solve the problem using software (e.g., create stand-alone app, information systems, online app, mobile app, or extend an existing software) and think of how you plan to achieve this.

Note: At the end of the subject, you will present an implemented software application of your proposed project. It is important to keep in mind that this is a 12-week project (4 weeks will be allocated to identifying project topic and requirements, 4 weeks will be on designing the project and 4 weeks will be allocated to implementing your project).

A good guide on defining the scope of your project is that it should have 4-6 major functions/features. The examples below will give you an idea of the level of complexity expected for your project.

Here are examples of possible projects (you can come up with your own idea):

1) Games (single or multi-player, no Artificial Intelligence required)
a) Board Games (Reversi, Connect Four, Checkers, Battleship, Scrabble, etc...)
b) Card Games (Blackjack, Poker, Solitaire, Uno etc...)
2) An application prototype where a user can add/edit/view records. There is no need to save data to files (use an in-memory database). Examples:
a) Sports results, fixtures, statistics, players ( for soccer, AFL, Rugby, Cricket, Basketball, Tennis or any sports you prefer)
b) Online banking - deposit, withdraw or view accounts
c) Food ordering - view menu items from restaurants; add, edit, delete orders

Document Proposal Format:

Your document should have the following format:

1. Title of the Proposed Project
2. Problem Description
o Describe the problem that you're planning to solve.
o Start a brief description of a high-level problem (few sentences) then describe some specific issues that you're interested in, then provide more specific details about the sub-issues that your work will solve.
3. Proposed Solution
o Describe how do you propose to address the identified problems
o Discuss the business value of your proposed solution. What will your customer and users gain from your proposed system?
4. Project Plan
o Discuss here the Software Process that you will use for your proposed project.
o Explain the activities in each of the stages (with the estimated timeline).
o Explain why this is the appropriate process for your proposed project

Assessment - Problem Analysis

Context
In software development, it is important to describe how a product will work entirely from the business stakeholders' view. A Software Requirements Specification (SRS) is used to describe all the capabilities a product must have in order to fulfil the business, stakeholder and user needs. Besides establishing a clear agreement between the software developer and customer on what the completed software must do, the SRS serves as a reference for testing and to address the needs of the operations and maintenance teams.

In Assessment 1 Part A, you were asked to submit a project proposal document describing the goals, objectives and plans for your project.

This assessment will demonstrate your understanding of software requirements analysis and modelling and help develop your business analysis skills as part of the software development team. Please ensure that you incorporate any feedback you were provided from Part A of this assessment.

Instructions

1. Develop a SRS Document that describes your proposed system and defines the inputs, outputs, functions, and attributes of the system, as well as the attributes of the system environment.
2. Use the Software Requirements Specification Template provided in Blackboard. You can add/remove items in the template depending on the applicability on your project. For example, if security and safety is not an issue then that section should be removed.
3. You can use any drawing tool in creating your requirements modelling diagrams. Refer to the learning materials discussed in Module 3 and 4 for example drawing tools that you can use.
4. You will be assessed on the correctness and completeness of your document:

a. Introduction and Overall Description
b. Functional and Non-functional Requirements
c. Requirements Analysis Model

Attachment:- Software Engineering Principles.rar