Program Specifications

Summary #

Programs contains multiple courses and this project is about accreditation of the programs.

MS Team #

link 2

Documents #

SRS PDF ATTACH #

Data model created by #

MS Access ATTACH #

Doc ATTACH #

Requirements #

Abreviations #

• AAC: Academic Assesment Center
• VRAA: Vice Rector for Academic Affairs
• DGS:

Managing program specifications

Details #

Two types of specifications #

1. undergraduate program
2. gradudate program

Each program will have atleast three courses. #

Each course should belong to only one program.

Services it depends on #

Course specifications #

To get course info

Adwar #

Info from Registrar #

Role management

Core features #

Fill form, submit, review, and send back or approve.

Form filling #

Some data is fetched from dependent systems and some is filled manually.

Solution Analysis #

1. Mayan EDMS
   • It document management, how does the document itself is created? According to the implementation form(wizard) is quite involved task.
   • What does it mean to work on a document? There are collaboration features, is it possible to change the doc, if yes how?
2. Form Tools With this Django you can preset user with series of forms, state is tracked, until the final form is submitted. form list
3. View Flow Django based BPMN Workflow with BPMN notation.
4. Django based Workflow Solution

Meetings #

Kickoff meeting <2021-03-07 Sun> #

Questions to ask? #

• [-] UI/UX

  • If not early on it will lead to redundant work for development team.
  • will help client to understand their product better
  • Finalize UI

• There are many fields to be entered, who are they going to divided?

  • There are sections in the requirements. These will be covered in the UX.

• How reviewer will so many fields to approve or reject? UX Ghaffar will take care

• Who will build API in course specification project? To fetch and populate the data.

• Adwar or Active directory ?

• ACC is DGS counter part for the undergraduate courses?

• VRAA is the final approver for both types?

• are we building for same the client? yes

• can designer can give UX now? yes

TODOs after the meeting #

• In Course specifications similar communication happens.
• Get access to it from Abdulla Joud
• Adwar is being used in course speicifications
• Yes

• Write an email to Hussain Muslim to get create project in the open projects.

• Meeting with Abdullah Joud and AbdulRahman about the course specificitions. Abdur Rahman was part of course specifications already.

• Meeting with developer

• Dependencies of the project?

  1. API’s in course specifications?
  2. ADWAR
  3. Registrar If not what changes needs by done and by whom?

Weekly PS meeting <2021-03-08 Mon> meeting #

Course specifications(CS) is stable for program specifications? #

No. There are issue in CS related to workflow, Camunda. Dr. Anas Confirmed that no changes needed in course specifications to use any part of it in program specifications.

Comment about changing requirements? #

mentioned.

Abdullah Joud, Hussain Muslem, Samani about integrations #

Partial or full integration with course specifications #

confirmed with Hussain Muslem, I can decide that.

UX meeting with Ghaffar <2021-03-10 Wed> meeting #

Questions to ask #

• Time and effort needed info is not shared yet with him, so not decided yet
• can built on top f course specifications UX will be decided in the next meeting

Meeting Minutes #

will update about next meeting, after reading the SRS.

Actions #

• He will need access to course specification
• Share SRS with

code and application walk through meeting #

Meeting with directory meeting #

Agenda #

1. Access
2. UI reusability
3. code reusability
4. Building API for this project
5. lessons learned and suggestions

Meeting Minutes #

1. Courses are being fetched from Banner initially, some will be entered.
2. UI/UX end at 47 minutes
3. We can explore and consider other workflow options in Django.
4. Already generating PDFs.

Code #

• How are you storing varies fields(structured/unstructured) structured

• versions? maintain history Initial course is version 0. AFter first approval, the version 1. AFter change triggers workflow and after final approval it becomes next version.

• Comments and sections associated?

• Camunda workflows? POST: Called at last page. GET: Happens at the beginning.

• Why you suggested doc manager? Mayan has own workflow engine.

Next Action #

• Camduna needed?
• Explore Mayan

Bader Ali ALDous said give an extension until one month <2022-06-16 Thu> and after that redirect them to him.