Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D DCST1008-studass-eksempel
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Alexander Moltu
  • DCST1008-studass-eksempel
  • Wiki
  • Home

Home · Changes

Page history
Create home authored Mar 14, 2022 by Alexander Moltu's avatar Alexander Moltu
Hide whitespace changes
Inline Side-by-side
home.md 0 → 100644
View page @ e41bb34d
### DCST 1008 Systemutvikling Group 2
*Members: Alexander Moltu, Jørgen T Nilsen, Magnar T Stokka, Mohammad Dabti, Mustafa Al-Doori*
**Description:**
We have created a To-do list application for desktops with all the necessary functions for an application of its type.
The application is built using the React and Electron frameworks, Bootstrap styles, and JavaScript. In addition, it makes database calls to store and retrieve data to and from a MySQL database.
The application renders a task list with the options to add, edit, delete, and complete tasks. In addition, there is also options to view completed tasks as well as add, edit and delete categories.
Each task consists of several attributes, of which some are necessary. Task name, category, and start- and end-date are all necessary attributes of a task. Without them, the task will become invalid and the application will hinder you to either add or save the task. In addition to these necessary attributes, there are optional attributes like priority status and description. These attributes are fully optional and will not affect the system in any significant way.
Each task has to be linked to a category. A task can not be created without choosing a category. As a result of this design we have incorporated a system to manage categories. In the category-page the user can add, edit and delete categories. A category consists of only two attributes, category-name and description, where only the name is a necessity.
The UI of the application has been designed in accordance with Don Normans 6 principles of interaction design. This is to meet all the requirements of universal design. This design decision includes the usage of high contrast elements in our UI and feedback to give the user a better response to their actions.
**Documentation**
****
* [Vision Document](/Vision-Document)
<br />
**Requirements**
****
* [Universal Design](/Universal-Design)
* [Usability Tests](/Usability-Tests)
* [Use Case Diagram](/Use-Case-Diagram)
* [Use Cases](/Use-Cases)
* [Domain model](/Domain-model)
* [Sequence diagrams](/Sequence-diagrams)
* [Wireframes](/Wireframes)
<br />
**System Documentation**
****
* [Project structure](/Project-structure)
* [Class diagram](/Class-diagram)
* [Persistence](/Persistence)
* [Source code](/Source-code)
* [Installation Manual](/Installation-Manual)
* [User Manual](/User-manual/.Overview)
* [Testing](/Testing)
\ No newline at end of file
Clone repository
  • Class diagram
  • Domain Model
  • Installation Manual
  • Persistence
  • Project Structure
  • Sequence Diagrams
  • Source Code
  • Testing
  • Universal Design
  • Usability Tests
  • Use Case Diagram
  • Use Cases
  • User Manual
    • Complete Task
    • Create new and edit category
    • Overview
View All Pages