Category | Assignment | Subject | computer science |
---|---|---|---|
University | Sheffield Hallam University (SHU) | Module Title | System Design and Development Project |
Word Count | 1000 – 1500 words |
---|---|
Assessment Title | Individual critical reflection |
During the module and the course you learn numerous techniques which allow you to design and build Web applications using ASP.NET MVC, XML and REST Web Services. This assignment gives you an opportunity to consolidate your skills, to investigate, design solution, and implement the concepts of a working Web application.
Assessment for this module is split into three parts. First part looks at developing a project idea, second part focuses on design and implementation of the project idea and final part is individual critical reflection of the project lifecycle. First two parts of the assessment will be undertaken as a team, team should have 3-4 members (2 is not a team and 5 is too many).
For this assessment you will be required to conceptualise a novel web application. Your application can utilise the technologies taught on the module. Each member of the team is required to take part in the analysis, design and development.
To ensure that the application is of the standard expected at this level your application should have a minimum of 15 functionalities. While considering your application idea it will be useful to bring in your prior experience from your first degree maybe or from work. This will allow you to bring in valuable domain knowledge which will make the idea more realistic.
For this submission you should produce following
Using feedback from presentation a final list of functional and non-functional requirements should be prepared by the team. These are the requirements you would then be expected to implement and the ones the Tutor will refer to when marking the application. You will be free to alter the requirements, but it will have to be like for like. Any changes to the requirements will have to be discussed with your project supervisor first.
This will be based on the requirements agreed in part A of the assignment. You will present your work in a presentation at the end of the module. During the presentation you will be required to demonstrate your application and how it fulfils the requirements agreed as part of first submission. Your presentation will be aimed at technical evaluators, to convince them on the feasibility of your ideas.
You must design your software development methodology. You have studied this as part of your course. You should use your chosen development methodology (Possibly design the method bespoke to your requirements ).
Strategy for collaboration
You must design for rich collaboration using collaboration tools and techniques for the process to include analysis, design and implementation.
Analysis and Design
Using your client or your supervisor as your client, you must develop your case study (For example, comprehensive use case diagram, use case descriptions) to help you to apply the process of analysis and design. This must lead to comprehensive conceptual designs (For example, class diagram) that would aid the implementation process.
Design of the application
Producing well documented design is an essential aspect of your project. You can use site maps, screen mockups/wireframe diagrams to help you document the user interface design.
Implementation of the application
Your designs (including strategy for collaboration and conceptual designs of the system) must clearly feature as input to your implementation process. Given the short timescale, your focus must be on converting your design to tangible implementation, and testing. Your implementation will demonstrate that design also features in the architecture of your application for effective features such as extensibility, scalability, and maintainability.
Your work will be evaluated on your ability to produce a well-designed and fully operational Web application. You are well advised to assess your own work - The example questions you should be asking yourselves are;
Refer to the marking matrix for a complete breakdown on the award of marks.
You will demonstrate your work using a presentation at the end of the module.
Individually, you will produce a short reflection including:
Are You Looking for Answer of This Assignment
Order Non Plagiarized AssignmentLook up your module’s BB site for the deadlines.
Here are the requirements for each submission
Assessment Criteria |
Assessment Criteria (0-39%) |
Assessment Criteria (40-59%) |
Assessment Criteria (60-79%) |
Assessment Criteria (80%+) |
Elucidation of the problem, Rationale, aims, objectives, and deliverable. 50% |
No clear explanation of the project. Does not establish the need and the rationale. It is not clear what the deliverable will be. No attention given to establishing some scope. |
Some limited understanding and elaboration of the problem. Limited outline of aims and objectives. Some attempt at identifying the scope but still not very clear. |
There is a clear project in terms of the problem at hand. There is clear and useful deliverable. There is clear scope in terms of what is in and what is out of scope. Elements are identified but they still need explaining. |
+ Project is well explained. Project is relevant to the aims and objectives of the module and of the course. Project encompasses / draws from learning in other modules (Goes across the course). Project uses knowledge domain that is relevant and appropriate. |
Proposed Approach, Method, Tools, Techniques 50% |
There is no clear plan for carrying out the project. Project, implementation methods, use of tools, allocation of work |
There is a method, with indication of technologies, tools, and allocation of work. But it is not thorough, somewhat flawed and subject to risk. |
Draws well from the project management module to clearly provide artefacts that demonstrate a coherent plan for use of technology, use of tools, allocation of work, and the timeline. |
+ Includes alternatives, recovery strategy, that demonstrate understanding of the implications if things do not go to plan. |
Task |
Mark |
Fail
|
50-59 (Pass) |
60-69 (Merit) |
70+ (1st) |
Management of the Project - Approach, methods, tools and techniques/strategies |
10 |
Little evidence of developing process, planning for using tools and techniques for collaboration, implementation, and testing |
Some indication/evidence of use of tools (For example Trello for collaboration, GitHub for implementation). Some techniques and strategies though approach is not fully fledged |
+ Good indication of use of tools and some indication of strategy for use such as Task Lists, To-do lists, project milestones |
+ Comprehensive use of tools with comprehensive approach for managing the project including use of project tracker, project milestones, project timelines |
Analysis and Design |
10 |
Lack of engagement with use of methods and techniques taught in the course |
Attempts to develop the case study, some indication of requirement analysis and use the technique to analyse findings. For example, may amount to incomplete/erroneous use case diagram, description, textural analysis leading to classes |
There is clear strategy for analysis and design: For example, compete/correct use case diagram and descriptions. Analysis of descriptions and clear path to a complete class diagram |
+ Strategy is complete and executed comprehensively: For example, use case diagram, descriptions, analysis process to design the class diagram is flawless, and it adheres to rules. Demonstrates insight and understanding of process and ability to apply |
Implementation of application requirements |
40 |
Has not attempted to fulfil all basic requirements. Requirements have been badly mis-interpreted |
Some of the requirements fulfilled, but functionality haven't been interpreted properly. |
Most requirements fulfilled. Good consideration given to potential ambiguity in requirements |
All requirements satisfied in a highly critical and perceptive manner keeping in mind the user group. Additional requirements identified, justified and deployed to enhance Web application. |
Application Architecture keeping in mind quality attributes such extensibility and scalability |
10 |
Application does not work, basic attempt at designing application architecture. |
3-tier architecture is established. |
Architecture is further split into layers such as data access layer. Implementation extends projects to make use of custom classes such as BEANs. |
Has extended the architecture and organised code with reuse and maintenance in mind. |
Approach to programming |
10 |
Code is structured poorly.
|
+ Some indentation in code. + Some of the variables, file names and functions named appropriately. |
+ Appropriate folder structure to segregate the code. + Most of the variables, file names and functions named appropriately. + Code blocks are commented well keeping in mind other developers who might use the code in future. |
+ Correct indentation in place throughout the application. + File names, variables and functions make it obvious to other developers the functionality coded. + Code is structured well to make it easy for other developers to maintain your application. |
Overall user interface design of Web application |
20 |
Design is incoherent and poorly presented. Required functionality is not exposed or difficult to establish. Usability has clearly not been considered. |
Design is basic but operational. + Some attention paid to usability. Flow and navigation reasonable. |
Application navigation is fluid and logical. Comprehensive use of event handling to provide enhanced User interface. Some user input validation |
User interface is made easy with use of controls such as dropdown boxes. Clear signs of rigorous User testing. Enhanced user input validations in place. |
Criterion |
0 - 30% |
30 - 49% |
50 - 59% |
60 - 69% |
³70% |
Present evidence of reflection on, and critical appraisal of the relevant processes and decisions 70% |
No real examination of the processes |
Inadequate or little examination of the processes. |
Processes and decisions examined. |
Processes and decisions well reviewed. |
Process and decisions comprehensively and critically reviewed. |
Reflection on individual contribution and future career development 30% |
No real examination of individual contribution and no future career plan present. |
Inadequate or some examination of individual contribution and future career plan present. |
Reasonable examination of individual contribution and future career plan present. |
Good examination of individual contribution and future career plan present. |
Sound examination of individual contribution and future career plan present. |
Buy Answer of This Assignment & Raise Your Grades
Order Non Plagiarized AssignmentAre you searching best assignment help for the solution of the System Design and Development Project Assignment? Then worry no need. There are specialized professionals for all categories of assignments who offer you plagiarism-free and superior content. You are assured that our Computer Science Assignment Help Service will make you productive and help you achieve high grades in your academic year. A free list of assignment samples written by PhD experts is also provided here that can help you boost your study power and check the quality of the report. So contact us today and get your top-notch assignment!
Let's Book Your Work with Our Expert and Get High-Quality Content