-
Notifications
You must be signed in to change notification settings - Fork 1
Home
Welcome to the Worlds Around™ wiki!
Our team had the first meeting where we discussed the project ideas. We discussed four main ideas :
- The first one was a platformer game
- The second one was a Airline Management System
- The third one was a Supermarket Management System
- Last but not least was the Epoka Football Club Managment System.
We discussed all the adventages and disadvanteges for each of the ideas and we came to the conclusion that is better to think a little bit more and decide in the upcoming week.
In the second week of our meeting we decided that our project will be a platformer game . We decided this idea because we have done managment systems in other subjects and we want to do something different. After this we discussed the technologies that we will be used . The programming language that we decided was Python and the libraries are pygame and diagram. One of our team member , Terens Tare did a short introduction how our game will be designed and then implemened. Terens , together with the other members of the team did a schema of how the game will be organized and main components that we will include.
During the third week, the focus is on developing a clear vision for the game, including its core mechanics, setting, and style. This involves identifying the target audience, determining the game's genre and platform, and outlining the key features and gameplay mechanics that will make the game unique and engaging. Once the initial planning is complete, the next step was to create sketches and designs for the game's assets and elements. This included concept art for characters, environments, and other assets, as well as detailed sketches of the game's levels, menus, and user interface. These designs will be used as a reference throughout the development process, helping to guide the creation of the final game. This process was very importent before we continue with the requirements of the game . By the way , each member is asked to think and write some requiremnts for the game that will be discussed next week.
The task discussed for this week involves several aspects of our project:
- The first part of the task involves identifying the requirements of the project, which includes various aspects such as functional dependencies, user interface requirements, learnability, accessibility, memorability, capacity, latency, monitoring, and user characteristics etc. The work division for these tasks is :
- Elvjo Fejzo ->Purpose and Scope of this Specification; Product/Source Description ; Product Context.
- Eralba Korbi -> User Characteristics ; Assumptions ; Constrains ; Dependencies.
- Emis Reka -> Functional dependencies (table).
- Enri Shtjefni -> User Interface Requirements .
- Eva Veli -> Domain Requirements ;Learnability; Accessibility ; Efficiency ; Memorability; Satisfaction; Capacity; Availability; Latency; Monitoring.
- Marvin Hoxha ->Maintenance ; Operations ; Standards Compliance ; Portability ; Security ; Protection ; Authorization and Authentication.
- Terens Tare -> Project Overview.
- The second part of the task involves adding more features to the game. This includes new gameplay mechanics, additional levels, new characters or environments, and other features that enhance the user's experience.
- The third part of the task involves a front-end discussion, where the design and layout of the game's interface are discussed. This include the use of graphics, color schemes, and other visual elements that help to make the game engaging and intuitive for the user.
- The final part of the task involves a back-end discussion, where the technical aspects of the game are discussed. This include the use of programming languages, databases, and other tools and technologies that help to ensure the game runs smoothly and efficiently. Arbin Bici and Terens Tare will start working with this part.
The task discussed for this week involves several aspects of our project:
1.The first part of the task involves prioritizing functional requirements. Functional requirements are the features or tasks that a software system needs to perform to meet the needs of its users. Prioritizing functional requirements involves identifying which requirements are most important to the success of the project and assigning them a priority level.
2.The second part of the task involves creating user scenarios, user cases, and use case diagrams. User scenarios are detailed descriptions of how a user interacts with the software system, while user cases describe specific interactions between a user and the system. A use case diagram is a graphical representation of the system's use cases and actors. These tools help to identify the system's requirements, and they provide a clear understanding of how the system should behave from the user's perspective.The work division for these tasks is :
- Emis Reka & Enri Shtejfni-> User Scenarios.
- Eva Veli & Eralba Korbi -> User Cases .
- Elvjo Fejzo & Marvin Hoxha -> Use Case Diagrams.
- Terens Tare & Arbin Bici -> Activity Diagrams.
3.The third part of the task involves identifying libraries and tools for the code. This involves selecting the software libraries and development tools that will be used to build the software system. These libraries and tools can include programming languages, frameworks, and third-party libraries that provide pre-written code for specific functions.
4.The fourth part of the task involves creating an entity-relationship diagram (ERD). An ERD is a graphical representation of the relationships between the various entities (such as objects, tables, and attributes) that make up a system. The ERD helps to identify the data requirements of the system and the relationships between those data elements. This diagram provides a clear understanding of how data flows through the system and helps to ensure that the system is designed to handle the data effectively. Terens Tare did the ERD.
No meeting and no assigned tasks for this week.
The task discussed for this week involves these aspects of our project:
1.Review the Use Case Diagram and apply changes to it before pushing it on GitHub
2.The second part The first part of the task involves creating different types of diagrams to help understand and visualize the behavior of a software system. State diagrams, collaboration diagrams, and sequence diagrams are all types of UML (Unified Modeling Language) diagrams used in software development. The work division for these tasks is :
- Emis Reka & Enri Shtejfni-> State Diagrams.
- Eva Veli & Eralba Korbi -> DataFlow Diagrams .
- Elvjo Fejzo -> Collaboration Diagrams.
- Marvin Hoxha -> Sequence Diagrams.
- Terens Tare & Arbin Bici -> Working on Code.
3.The third part of the task involves defining the background of the game. This includes the game's setting, storyline, characters, and other background details. Defining the background helps to establish the game's overall tone and atmosphere and provides a foundation for the game's design and development.
4.The fourth part of the task involves creating sound effects and music for the game. Sound effects are used to enhance the player's immersion in the game by providing audio feedback for actions taken by the player or events that occur in the game world. Music sets the tone for the game, creating an emotional response in the player and helping to establish the overall atmosphere of the game. Developing a consistent and high-quality audio experience is essential for creating an engaging and immersive game.
The task discussed involves several aspects related to software development and game design:
1.State diagrams: State diagrams are graphical representations that depict the various states of a system or an object and the transitions between those states. They are commonly used to model the behavior and lifecycle of objects in a software system. State diagrams help visualize the flow of control and data within the system, allowing developers to understand how the system behaves in different scenarios.
2.Data flow diagrams: Data flow diagrams (DFDs) illustrate the flow of data within a system or a process. They show how data is input, processed, and outputted throughout the system. DFDs use various symbols to represent data sources, processes, data storage, and data destinations. These diagrams help in understanding the data flow and transformations within the system, enabling better analysis and design of the system's functionality.
3.Collaboration and sequence diagrams: Collaboration diagrams, also known as communication diagrams, illustrate the interactions and relationships between objects in a system. They show how objects collaborate and exchange messages to accomplish a specific task or scenario. Sequence diagrams, on the other hand, depict the chronological sequence of interactions between objects, including the messages exchanged and the order of execution. Both collaboration and sequence diagrams provide a visual representation of the dynamic behavior of a system and aid in understanding the communication and interaction patterns.
4.Characters of the game: Characters are the virtual entities that players interact with within the game world.
5.The work division for next week is :
- Terens Tare & Enri Shtejfni-> Deployment Diagrams.
- Eva Veli & Eralba Korbi -> Class Diagrams .
- Elvjo Fejzo & Arbin Bici -> Component Diagrams.
- Emis Reka & Marvin Hoxha -> Object Diagrams.
- Terens Tare & Arbin Bici -> Working on Code.