search

BenjaminTham-SIT / INF2001_P4-5

INF2001 Introduction to Software Engineering
0 stars 0 forks source link

[1.1.5] Project Clarification #2

Closed BenjaminTham-SIT closed 11 months ago

BenjaminTham-SIT commented 1 year ago

‼Important notice: Due to a significant lack of understanding of Github and Github Project Boards, this issue has been created later than actual start date and end date. The team has been informed that as this is a week 1-3 issue, it will not be challenged against the rubrics.

About:

Description

Introduction to SE project requires many clarifications and enquiries. In order to perform to best of our abilities, we should ensure any doubts and enquiries are to be cleared as soon as possible. This is to ensure a more streamlined execution of the project.

Questions & Enquiries

  1. General project inquiry Can we get a general direction for this project? This includes a concise description of this project objective and project goal, as well as an idea of a final product for every milestone (milestone 1, milestone 2, milestone 3, final product) Due to the vagueness of the project description, we would like a general guide in the right direction and professional advise from the professors.

What is the project objective? We would like a detailed idea of what this project aims for us to achieve. We wish to understand what the main idea of this project would be, project objectives and project goals. We believe that a clearer understanding of these information is extremely important in producing a high quality work that is both an independent work of our own but still remaining impartial from the professors help. Is this project a: -business management focused -team based and team cohesion (how well the team works together) focused -software development process and software development cycle based project -design focused -Information Technology development focused ...project?

What is the project specification? The team understood that we are supposed to come up with a hypothetical software that suits and aligns with the project description. However, we are unable to understand and see a final product/final solution that is to be presented. Are we supposed to produce mockups using tools such as photoshop, Figma or any rendering tool? storyboards like this: https://s3.amazonaws.com/assets.fullstack.io/n/20210926170551558_storyboard.png mockups like this: https://goodmockups.com/wp-content/uploads/2017/06/Free-Mobile-App-Screens-Presentation-Mockup-PSD.jpg Or are we expected to deliver an actual working product that can be immediately implemented? Would you be expecting to see actual results appearing if they key in values into the software (for example to be able to actually see the employees registered and their working hours)? an actual working app like this: https://www.projectmanager.com/wp-content/uploads/2022/11/workload-chart.webp

...If the project is expecting a mockup, how detailed would you be expecting? We would like to know how detailed would the mockup's need to be and of what quality and standard would be expected. Do the mockups have to have titles drawn across to describe the details of the product as well as linkages from one mockup board to the other?

What is the project expectation? We are wondering how well would the project, and most importantly how detailed would the report have to be in order to be considered an excellent project. This includes the Kanban board, the Gantt chart, and the repository. What level of professionalism would the you be expecting? How frequently would you hope we update these? Regarding the report, we understand that there is an importance on relevancy based on the things we write, but what level of detail would you hope from our report? What separates an excellent report from an average one from a terrible one?

  1. Technical project inquiry We hope to develop a better understanding of the more technical side of this project. This includes stuff that may or may not be outside the curriculum, hence we understand if certain questions can be answered in the lectures.

Use case diagrams and UML Within the first few weeks, this would be one of the main deliverables. Hence, a huge emphasis would be placed on the UML and use case diagrams. We would like to know more about the relevancy of the UML/use case with this project. Due to the vast amount of UML's variations existing, we would like to know is there a specific few that we are to use ONLY? Or we are allowed to use any UML's and use cases as long as they fit our project description? How many of these diagrams are we recommended to come up with? As many as possible or a handful that are detailed enough? How detailed are we supposed to explain and elaborate on these diagrams? Like the question previously asked, are we expected to draw callout titles and callout arrows to describe each individual parts? Also, if it is allowed, can we have an example?

Kanban board Regarding the kanban board, there is apparently a certain procedure on how we are supposed to write it up. Is this true? Or we can write up anyway we see fit? Also, are we expected to note down every single thing we plan to do and update them very frequently?

Client question This may have to be forwarded to our respective clients but we are hoping that we can attain some answers from you. What are the expectations like when asking questions? This means that what are the kind of questions would a typical client be expecting. Clear, concise, simple, direct and aided with many images and visuals? Also, how important are visual aids during the questioning of a client? This is because we believe that having visuals are much, much better than just simply talking and writing things down.

Professors contact information Should any of the questions be difficult to answer, I was thinking is it possible to leave contact information of other professors who may be able to provide more information with those said questions. Currently I only have contact information of the tutorial prof (Serena Goh), the module lead and the co-module lead

Goals:

Objective

Due to the vagueness of the project, every single enquiry are to be FULLY RESOLVED UNTIL CLARIFIED. Ensure that every prof answer our questions and clear every single doubts. If one isn't able to help, immediately approach the other. Alternatively we can forward or carbon copy the email to every prof available.

!!!Be as persistent, stubborn and pressed as possible for a proper answer!!!

Success - Completion Details:

Task Status:

Priority:

Notes:

Professor's email collective (add as necessary)

**Asst. Prof. Alex Q. Chen (Module Lead)**
e-mail: Alex.Q.Chen@SingaporeTech.edu.sg

**Assoc. Prof. Indriyati Atmosukarto  (Module Co-lead)**
e-mail: indriyati@singaporetech.edu.sg  

**Labtorial Instructor Serena Go**
e-mail: af_serena.goh@singaporetech.edu.sg
BenjaminTham-SIT commented 1 year ago

Image

BenjaminTham-SIT commented 12 months ago

Work Done:

Email Prof Serena

Repository Commit status:

No commits

Completion Deadline Effect:

More details are required for full project completion effects

Changelog:

[2/9/2023] - Email sent to Prof Serena [4/9/2023] - Email sent to Prof Alex [4/9/2023] - Email sent to Prof Indriyati [6/9/2023] - Zoom meeting with Prof Serena

Start Date - End Date:

2/9/2023 - 6/9/2023