Skip to content

Functional Specification

Jump to bottom Edit New page
Olga Shiryaeva edited this page Jun 6, 2018 · 9 revisions

The application should meet the following requirements:

  1. Store customers with their name, mobile phone and email
  2. Record information about orders: price for repair and time spent by mechanic
  3. Keep track of spare parts in stock
  4. Automatically calculate price based on spare parts used and time elapsed
  5. Control security permissions for screens, CRUD operations and attributes of records
  6. Perform Audit of critical data changes
  7. Provide API for a mobile client to place an order

Data model is shown in the picture below:

Data model

next →

Add a custom footer

Home

  1. FUNCTIONAL SPECIFICATION

  2. CREATING A NEW PROJECT

  3. DEFINING DATA MODEL AND CREATING THE DATABASE

    3.1 Client Entity

    3.2 Mechanic Entity

    3.3 SparePart Entity

    3.4 OrderStatus Enum

    3.5 Order Entity

    3.6 Generate DB Scripts and Create the Database

  4. AUTO-GENERATED CRUD UI

    4.1 SparePart CRUD UI

    4.2 Client CRUD UI

    4.3 Mechanic CRUD UI

    4.4 Order CRUD UI

  5. FIRST LAUNCH

    5.1 Generic Filter

    5.2 Security Setup

    5.3 Audit

    5.4 First Launch Conclusion

  6. DEVELOPMENT BEYOND CRUD

    6.1 Integration with IDE and Project Structure

    6.2 Customization of Existing Screens and Hot Deploy

    6.3 Business Logic Development

    6.4 REST API

  7. Conclusion

Clone this wiki locally