| 3 | | Trac is a '''minimalistic''' approach to '''web-based''' management of |
| 4 | | '''software projects'''. Its goal is to simplify effective tracking and |
| 5 | | handling of software issues, enhancements and overall progress. |
| 6 | | |
| 7 | | All aspects of Trac have been designed with the single goal to |
| 8 | | '''help developers write great software''' while '''staying out of the way''' |
| 9 | | and imposing as little as possible on a team's established process and |
| 10 | | culture. |
| 11 | | |
| 12 | | As all Wiki pages, this page is editable, this means that you can |
| 13 | | modify the contents of this page simply by using your |
| 14 | | web-browser. Simply click on the "Edit this page" link at the bottom |
| 15 | | of the page. WikiFormatting will give you a detailed description of |
| 16 | | available Wiki formatting commands. |
| 17 | | |
| 18 | | "[wiki:TracAdmin trac-admin] ''yourenvdir'' initenv" created |
| 19 | | a new Trac environment, containing a default set of wiki pages and some sample |
| 20 | | data. This newly created environment also contains |
| 21 | | [wiki:TracGuide documentation] to help you get started with your project. |
| 22 | | |
| 23 | | You can use [wiki:TracAdmin trac-admin] to configure |
| 24 | | [http://trac.edgewall.org/ Trac] to better fit your project, especially in |
| 25 | | regard to ''components'', ''versions'' and ''milestones''. |
| | 2 | = RouteMK |
| 40 | | For a complete list of local wiki pages, see TitleIndex. |
| | 13 | Under mentorship of: professor Vangel Ajanovski, PhD |
| | 14 | |
| | 15 | |
| | 16 | |
| | 17 | |
| | 18 | == Brief project summary |
| | 19 | |
| | 20 | |
| | 21 | A centralized online general transport ticketing system that enables users to conveniently purchase tickets for various means of transport through a single platform. The application includes features for searching available routes, selecting preferred dates, times, and seating or travel options, and completing transactions securely online. Users can create accounts to store ticket history and receive notifications about their bookings. Additionally, the system provides functionalities for operators to manage schedules, monitor seat availability, and update routes in real time. This centralized approach enhances the user experience by streamlining ticket purchases, reducing wait times, and offering quick access to information across different transport providers and routes. |
| | 22 | |
| | 23 | == Members\\ |
| | 24 | ||= Name =||||= Index =|| |
| | 25 | ||Kristijan Stojanovski (Coordinator)|||| [[span(**222077**)]] |
| | 26 | ||Jana Angjelkoska|||| [[span(**221507**)]] |
| | 27 | ||David Dukoski|||| [[span(**221514**)]] |
| | 28 | |
| | 29 | == Phases and coordination |
| | 30 | ||= Phase =||||= Name of Phase =||||= Status =||||= Date =|| |
| | 31 | ||''P0''||||'''[wiki:DefiningTheProject Defining the project]'''|| |||||| || |
| | 32 | ||''P1''||||'''[wiki:ConceptualModel Conceptual model (ERD)]'''|| |||||| || |
| | 33 | ||''P2''||||'''[wiki:RelationalSchema Relational schema (DDL and Database)]'''|| |||||| || |
| | 34 | ||''P3''||||'''[wiki:ApplicationDesign Application design - Everyday scenarios and use cases ]'''|| |||||| || |
| | 35 | ||''P4''||||'''[wiki:AnalyticalStatisticalQuerying Analytical and statistical querying ]'''|| |||||| || |
| | 36 | ||''P5''||||'''[wiki:PrototypeApplication Prototype application]''' || |||||| || |
| | 37 | ||''P6''||||'''[wiki:Normalization Normalization ]''' || |||||| || |
| | 38 | ||''P7''||||'''[wiki:ApplicationDevelopment Application development]''' || |||||| || |
| | 39 | ||''P8''||||'''[wiki:Security Security ]''' || |||||| || |
| | 40 | ||''P9''||||'''[wiki:Optimization Optimization ]''' || |||||| || |
| | 41 | |
| | 42 | |
| | 43 | |
| | 44 | |
