-
Notifications
You must be signed in to change notification settings - Fork 1
Elvjo Fejzo
Choosing a project to focus on was our top priority during the first week. Four of the concepts that emerged after we generated many more and thoroughly discussed each one were chosen. Ultimately, our group chose to create a platformer-style game. We also talked about the technology that will be used in our project. First, because of its straightforward syntax and widespread familiarity, we decided to choose Python as our primary programming language
After deciding on our concept, it was time to begin developing the game's basic design and functionality. I conducted some study on typical game development ideas and the internal workings of games like ours. I gave the idea to work with a game engine like Godot. I presented these ideas to the team during our meeting, and we talked about them and tried to make them better. After that, we discussed design concepts brought up by other team members in an effort to come up with a final design that we could all agree on and consider appropriate.
We worked on our project's specification specifics this week. We were each given a different section of the requirements to work on. This third week is spent establishing a clear vision for the game, including its fundamental mechanics, setting, and aesthetic. The target market must be identified, the game's genre and platform must be chosen, and the major elements and gameplay mechanics that will distinguish the game and keep players interested must be described.
This week, once we settled on a general direction for the game, I worked on drafting some part of the requirements specification for the project. This involved working on a number of key components, including the Purpose and Scope of the Specification, the Product/Service Description and the Product Context.
In the fifth week I worked on use case diagrams. A use case diagram is a graphical representation of the system's use cases and actors. These tools aid in determining the system's needs and give a clear idea of how the system ought to operate from the viewpoint of its users.
Midterm Exam Week.
This week we started creating different types of diagrams to help understand and visualize the behavior of a software system. I worked on Collaboration Diagrams. A collaboration diagram, also known as a communication diagram, is an illustration of the relationships and interactions among software objects in the Unified Modeling Language (UML). We can use these diagrams to portray the dynamic behavior of a particular use case and define the role of each object.