Embedded Files
In order for students to be able to develop software to meet an identified need, they first need to be able to understand the specifications of a problem so that they can eventually translate these specifications into code. As well as having good technical skills, it is necessary for students to have good communication skills so that the users’ requirements can be fully understood and implemented throughout the development process. The modelling tools used should conform to those specified in the Software and Course Specifications document and should provide documentation that can be interpreted by developers and maintainers. Students should develop and refine skills as an integrated part of developing their software solutions. It is important at this initial stage of the process that all relevant social and ethical issues are considered as an integral part of the design and development of the solution. [NESA SDD Syllabus 2010]
Recommended Tools for Diagramming
Recommended Tools for Diagramming
draw.io, lucidcharts, pencil & paper
The tools we study can be used used for both understanding and design. Remember, "One Level’s Requirement Is Another Level’s Design".
Defining & Understanding the Problem
Defining & Understanding the Problem
- identifying the problem (needs of the client)
- functionality requirements
- compatibility issues
- performance issues
- boundaries of the problem, scope
This is often assembled in to a problem statement and a Software Requirements Specification (SRS).
Issues relevant to a proposed solution
Issues relevant to a proposed solution
Determining if an existing solution can be used– social and ethical considerations
- consideration of existing software products
- customisation of existing software solutions
- cost effectiveness
- licensing considerations
Selecting an appropriate development approach if there is no appropriate existing solution
Design Specifications
Design Specifications
Developer’s perspective
Developer’s perspective
- Data types, Structures and Variables
- Data Dictionary
- One for overall program
- One for each array of records / database table
- Data Dictionary
- Software design approach
- Modelling & Documenting the system
- Context Diagram & Data Flow Diagrams
- IPO diagrams (external link)
- one for each process in DFD
- use 3 column layout for this course!
- System Flow Chart
- Structure Chart(s)
- Algorithms - Pseudocode and/or Flowcharts
- One for each procedure in Structure Chart
- Storyboards (external link)
- Test Data and Expected Output - TODO Create page
User’s perspective
User’s perspective
- Interface design
- Storyboard (required by HSC SDD)
- Annotated Wireframes and/or Mockups
- Appropriate messages
- Appropriate icons
- Relevant data formats for display
- Ergonomic issues
- Relevance to the users environment and computer configuration
- Social and ethical issues
Communication between client and developer
Communication between client and developer
- the need to consult with the client
- the need to incorporate the client’s perspective
- the need for the developer to enable and consider feedback
- the need to involve and empower the client during the development process
representationaltools-090709091427-phpapp02.pdf- Pilot - With the Pilot method of implementation (or conversion), the new system is installed for a small number of users. These users learn, use and evaluate the new system. Once the new system is deemed to be performing satisfactorily then the system is installed and used by all. (Davis.S, (2001) Software Design and Development: The HSC Course.)
Report abuse