design template for project, Cheat Sheet of Software Development

Download design template for project and more Cheat Sheet Software Development in PDF only on Docsity!

NUP1: Software Solution

Design Template

[Company]

Software

Project

Template

[Name of Project]

[Student Name] [Date] [Version x.x]

Contents

• A. Introduction................................................................................................................................................................
• A.1. PUrpose Statement..................................................................................................................................................
• A.2. Overview of THE PROBLEM.....................................................................................................................................
• A.3. Goals and Objectives...............................................................................................................................................
• A.4. Prerequisites............................................................................................................................................................
• A.5. Scope........................................................................................................................................................................
• A.6. Environment............................................................................................................................................................
• B. Requirements..............................................................................................................................................................
• B.1. Business Requirements...........................................................................................................................................
• B.2. User Requirements.................................................................................................................................................
• B.3. Functional Requirements........................................................................................................................................
• B.4. NonFunctional Requirements.................................................................................................................................
• C. SOFTWARE DEVELOPMENT METHODOLOGY.............................................................................................................
• C.1. Advantages of the waterfall method......................................................................................................................
• C.2. disAdvantages of the waterfall method..................................................................................................................
• C.3. Advantages of {A DIFFERENT METHOD}.................................................................................................................
• C.4. disAdvantages of {A DIFFERENT method}...............................................................................................................
• C.5. best SUITED.............................................................................................................................................................
• D. Design.........................................................................................................................................................................
• D.1. Storyboard or Flowchart (Change title to fit needs)...............................................................................................
• D.2. UML Diagram (Change title to fit needs)................................................................................................................
• D.3. GUI (Change title to fit needs)................................................................................................................................
• E. Testing.........................................................................................................................................................................
• E.1. Testing Type (change name to fit your needs)........................................................................................................
• E.1.1. Test Name 1.........................................................................................................................................................
• E.1.2. Test Name 2.......................................................................................................................................................
• E.1.3. Test Name 3.......................................................................................................................................................
• F. Sources......................................................................................................................................................................

B. REQUIREMENTS

Provide a brief introduction on requirements. You may select the correct subsections that match the

needs of your solution and the key requirements that you identified from the profile document.

Note: All requirements must be in your own words and interpret the requirements found in the “CRM

Requirements” attachment. Please do not copy and paste word for word from the requirements in the

“CRM Requirements” attachment.

B.1. BUSINESS REQUIREMENTS

Provide a brief introduction to the business requirements for the proposed system.

B.2. USER REQUIREMENTS

Provide a brief introduction to the user requirements for the proposed system.

B.3. FUNCTIONAL REQUIREMENTS

Provide a brief introduction to the functional requirements for the proposed system.

B.4. NONFUNCTIONAL REQUIREMENTS

Provide a brief introduction to the nonfunctional requirements for the proposed system.

C. SOFTWARE DEVELOPMENT METHODOLOGY

The company has selected the waterfall software development methodology for this project. Examine

the waterfall methodology and compare it to other software development methodologies (e.g., Agile).

Include a brief introduction to the development process as well.

Note: All subsections are required. Refer to the requirements section and rubric section of the assessment

for additional information.

C.1. ADVANTAGES OF THE WATERFALL METHOD

Describe the advantages of the waterfall methodology and how they will benefit this project.

C.2. DISADVANTAGES OF THE WATERFALL METHOD

Describe the disadvantages of the waterfall methodology and how they may hinder this project.

C.3. ADVANTAGES OF {A DIFFERENT METHOD}

Describe the advantages of a different methodology and how they will benefit this project.

C.4. DISADVANTAGES OF {A DIFFERENT METHOD}

Describe the disadvantages of a different methodology and how they may hinder this project.

C.5. BEST SUITED

Describe why the waterfall methodology is the best software development methodology for this project.

OR

Provide the details of a different development process and outline why you would have selected it and

how it would have been better suited for this project.

D.2. UML DIAGRAM (CHANGE TITLE TO FIT NEEDS)

Provide a set of UML diagrams that cover the proposed solution. This can include but is not limited to

class diagrams, database diagrams, and use case diagrams. Also, ensure that all diagrams are clearly

discussed and noted.

Figure 2 : Sample Database

D.3. GUI (CHANGE TITLE TO FIT NEEDS)

Provide a mock-up of the proposed GUI forms that will be used in the proposed solution. Also, clearly

indicate where the GUI components point inside the application.

Figure 3 : Sample GUI Mock-up GUI Control Mapping ID Control Property Data Source 1 Textbox On application open text = “” or null NA 1 Textbox On click of button text = “Hello World” Internal Variable 2 Button On click change text of textbox 1 to “Hello World” Internal Variable 3 Form Text= “Hello World”

E.1.2. TEST NAME 2

Requirement to be tested

Preconditions: Conditions that must be present before test case can successfully run

Steps: The steps the tester must execute to test the feature.

Expected results: Expected results and any side effects such as updating a database, writing to a file,

etc.

Pass/Fail: Mark whether the test case passed or failed. The results can be compiled and used to

determine if the application is ready for delivery/release.

E.1.3. TEST NAME 3

Requirement to be tested

Preconditions: Conditions that must be present before test case can successfully run

Steps: The steps the tester must execute to test the feature.

Expected results: Expected results and any side effects such as updating a database, writing to a file,

etc.

Pass/Fail: Mark whether the test case passed or failed. The results can be compiled and used to

determine if the application is ready for delivery/release.