Meetings

[robinziegler]

Meeting Dokumentation

TINF21C, SWE

Client:

• Markus Rentschler
• Christian Holder

Projectteam 4: Dana Frey, Maximilian Trumpp, Nils Hoffmann, Michael Grote, Fabian Kreuzer, Robin Ziegler

Version | Date | Author | Comment -- | -- | -- | -- 0.0 | 30.09.2022 | Robin Ziegler | -

[DanaFrey]

Meeting-Protocol 03.10.2022, 3 PM to 4 PM

meeting held via Teams

• discussion about application: we don't have the latest version of the application
• discussion about the main goals of our project and distributing roles: -> Business Case (Robin Ziegler) and CRS (Max Trumpp) -> SAS (Fabian Kreuzer, Nils Hoffmann) -> SRS (Dana Frey) -> project organization (Michael Grote) -> documentation -> presentation
• discussion about a time frame, in which the assigned tasks should be finished -> Agreement: 11.11. latest submission date (time frame of 6 weeks) -> trying to get the work done by 16.10.

[DanaFrey]

Meeting-Protocol 14.10.2022, 9.45 AM to 10.15 AM

meeting held in person

Dicussion about the project's tasks in greater detail.

• file import should also display file types other than the ones it already shows
• summing up the 'import' and 'open' buttons to 'save' and 'save & close buttons
• improve 'easy mode' -> remove right side of program -> only be able to add data values
• remove top right side of program
• values, which are marked in red are errors -> the cursor should point to the editor window in which such error occurs
• product code -> device name
• data model should change data set
• data model should always be fully opened to view all the data available
• option to open file by right-clicking instead of a 'drag & drop' window
• standalone project: no installer only .exe file

Current occurring errors:

• .amlx files which were saved before are not capable of being opened again (might be the case for other file typed as well)
• data model disappears after error

[DanaFrey]

Meeting-Protocol 20.10.2022, 4.40 PM to 5.40 PM

meeting held via Teams

Discussed the documents of all team members:

• documents could be more consistent than they are now ->introduction should be the same in all the documents, that contain an introduction -> document’s version should start with 0.x instead of 1.x
• discussed smaller issues about certain documents
• upload documents to “Wiki” Tab in the project’s repository
• documents should have a work time of approximately 10 hours each

Other:

• GANTT-chart and PSP needs to be done • Keep track of project work time and note it down into GitHub repository • Start with presentation at the next held meeting (most likely next Friday 28.10.)

[DanaFrey]

Meeting-Protocol 28.10.2022, 9.45 AM to 10.30 AM

meeting held via Teams

Meeting topics:

• „Usability Analysis“
• Presentation (who works on it and how we should organize it)
• Rather or not we should use wiki on GitHub or use word documents -> Use wiki and if existing, upload word documents to GitHub
• Use Cases

[DanaFrey]

Meeting-Protocol 10.11.2022, 3:30 PM to 4:00 PM

meeting held in person

Meeting topics:

• the problems and errors the program has (especially the problems in terms of the code)
• went through the presentation together -> changed some things -> discussed who is going to present and what they are saying (Robin and Max will do the presentation, then Fabian will review the program and its issues)

[DanaFrey]

Meeting-Protocol 09.03.2023, 12:45 AM to 1:30 PM

meeting held in person

Introduce Sophie as a new team member to our project.

Meeting topics:

• should we throw out old GUI and SET up a new one or update old GUI -> exchanged ideas, how new GUI could look like

• exchange information we gathered about the program and its structure

• discuss advantages and disadvantages of different GUI building programs: -> WPF: beginner-friendly, toolbox, good documentation -> WinUI 3: more recent, not very user-friendly -> Forms: very old, was used by previous team

• open question: Which GUI program should we use?

• open question: Instead of an installer, should we implement a single .exe file or a folder with all necessary files in it?

• open options, which we need to discuss with Herr Rentschler: -> Option 1: Work on existing program functionalities, maybe even rewrite them as a whole and try fixing bugs so that future teams can actually work with the project -> Option 2: Set up new GUI and rewrite existing program functionalities, so that they work on our new GUI

[DanaFrey]

Meeting-Protocol 21.03.2023, 11.45 AM to 12.15 AM

meeting held in person

Meeting topics:

• went through Usability analysis by Nils and Sophie
• certificates -> What exactly is a certificate in our program -> data type of certificates -> dialogue for certificate selection?
• GitHub -> should add Business Case and PM to Wiki -> Which branches can be merged into master branch? -> Which branches to we need? -> One branch per developer? -> create issues based on issues from Usability Analysis -> create Milestones -> create Manual

[DanaFrey]

Meeting-Protocol 17.03.2023, 11.00 AM to 11.45 AM

meeting held via Teams

Customer presentation day

• presentation of our Usability Analysis Powerpoint
• customer asks for another meeting, where our team should present further plans and first looks into new UI

[DanaFrey]

Meeting-Protocol 29.03.2023, 10.30 AM to 11.00 AM

meeting held via Teams

Customer presentation day

• presentation of Usability Analysis document, which includes issues our team is working on and gave customer first looks into UI prototyp

Following notes are improvements given to us by our customer

• "help" menu point shoould keep sup-points "About" and "Help"
• no 90s style look of program
• white spaces in "Generic Data" field should be collapsable
• issues in Usability Analysis document should either be shown in a table or arranged by chapters
• name of the program should be "Modelling Wizard (Version) (Date)" instead of "WinUI Desktop"
• font size should be the same at "Attributes" tab
• documents should no only be updated with new information coming from our project instead of the older ones
• SAS -> "code quality" should be a chapter -> chapters should be labeled with numbers (e.g. 1.0 Introduction) -> future steps shouldnt be mentioned -> no "Usability Concept" -> no "color theme" -> one capter called "Quality Goals" which includes anything dealing with quality

[DanaFrey]

Meeting-Protocol 14.04.203, 10.45 AM to 11.45 AM

meeting held in person

Customer presention and getting advises

Usability advises:

• clear difference between menu bar (which includes program options like 'About') and sub menu bar (which includes Generic Data,...)
• the top right corner should contain the whole file name for better overview on the file we are currently working on, the file name is made from the 'device name' + the 'vendor' which can also be found in the top right corner of the old project
• clickable fields shouldn't be too small
• a message saying 'there are unsaved changes' should appear after changing values

General advises:

• Manual should be opened in an external browser instead of having a Github linking in the program itself
• there should be one 'main' object, which includes every other object
• there should be a clear difference between frontend and backend, backend logic or code should never randomly appear in some sort in the actual frontend

Old project and new project:

• mandatory attributes (which are marked in red in the old project) should be visible and should turn green after a value has been written into
• AML file should be parsed and values should be read out from it (was already done in the old project, but not every value was read)
• SystemUnitClassLib is the central element out of the AML file, it contains every value that should be read and displayed
• 'Attachments' should be saved as a separate file in the package and should be linked to it
• attrubute groups should be collapsible (in old project they were shown as normal attributes even though they were the headline for more attributes to come underneath)

New Feature:

• there should be a start screen which includes two options to click on:
• Option 1: New project/file (does what it says + opens prompt for name + id)
• Option 2: Open project/file (does what it says)

[DanaFrey]

Meeting-Protocol 28.04.2023, 10.30 AM to 11.30 AM

meeting held via Teams

Discussion with Christian Holder and intern

• rename "Generic Data" to "Roleclass"
• compare old and new Modelling Wizard in final presentation
• "What we have learned" chapter in final presentation
• a live presentation would be better than a presentation
• first presentation then present tool live

[DanaFrey]

Meeting-Protocol 09.05.2023, 11:00 AM to 11.30 AM

meeting held in person

• Robin Ziegler will implement tests
• Nils Hoffmann will create a user manual
• development and coding stop on the 09.05.2023
• last refactoring and small adjustments
• Version 3.0 will be the final version of the Modelling Wizard
• all documents from the wiki must be available in a .pdf format

Presentation

• Chapter: utilized tools/ guidelines (perhaps talk about why we used the specific tool and compare it to others) => Robin Ziegler
• Chapter: Comparison old Wizard -> new Wizard => Sophie Kirschner
• Live Demonstration of Modelling Wizard => Maximilian Trumpp

[DanaFrey]

Meeting-Protocol 12.05.2023, 8.45 AM to 9.30 AM and 10.50 AM to 11.20 AM

meeting held in person

Feedback received from Markus Rentschler regarding each team members

Robin Ziegler (Business Case, STR):

• include screenshot of Modelling Wizard
• update in general
• add Sophie Kirschner as a team member in STR

Nils Hoffmann (User Manual):

• update pdf of to 1.0

Dana Frey (SRS):

• correct wiki headline
• remove first prototype from NF11 (GUI ) and link Sophie Kirschner's Usability Concept
• update Modelling Wizard screenshots in a more readable way
• remove NF12 and add included text to NF11
• change 'easy mode' and 'expert mode' from NF to LF
• description text for enhancements
• • add Sophie Kirschner as a team member in pdf's cover page

Fabian Kreuzer (SAS):

• update (correlation is not clear enough)
• number each chapter
• link source code
• describe, how the source code is organized

Sophie Kirschner:

• create a seperate glossar, which each team member can link

Michael Grote (PM):

• update