Phase stringclasses 6
values | Question stringclasses 45
values | Person stringclasses 6
values | Answer stringlengths 13 154 |
|---|---|---|---|
Requirements Analysis | Q1: How were the initial requirements for the LMS gathered? Was there any formal requirement-gathering process like interviews, surveys, or workshops? | Imtiaz Ahmed | Requirements were gathered by exploring open-source LMS platforms (e.g., Moodle) and consulting IT team members. |
Requirements Analysis | Q1: How were the initial requirements for the LMS gathered? Was there any formal requirement-gathering process like interviews, surveys, or workshops? | Javid Hussain | Requirements were gathered through discussion-based sessions initiated by Dr. Irshad Hussain with a committee of faculty members, IT staff, and an intern. |
Requirements Analysis | Q1: How were the initial requirements for the LMS gathered? Was there any formal requirement-gathering process like interviews, surveys, or workshops? | Tahawur Abbas | Requirements were collected via student interviews and admin meetings, with formal interviews and meetings conducted. |
Requirements Analysis | Q1: How were the initial requirements for the LMS gathered? Was there any formal requirement-gathering process like interviews, surveys, or workshops? | Amjad | Requirements were gathered through comprehensive requirement analysis sessions, including interviews and regular meetings with stakeholders. |
Requirements Analysis | Q1: How were the initial requirements for the LMS gathered? Was there any formal requirement-gathering process like interviews, surveys, or workshops? | Asad Ali | Requirements were gathered through meetings; formal documentation was not prepared. |
Requirements Analysis | Q1: How were the initial requirements for the LMS gathered? Was there any formal requirement-gathering process like interviews, surveys, or workshops? | Muhammad Askari | Requirements were gathered through informal stakeholder meetings rather than formal documentation processes. |
Requirements Analysis | Q2: Were stakeholders such as faculty, students, or admin staff involved during the planning stage? | Imtiaz Ahmed | Yes, students (Amjad, Tahawar, Abida) and some faculty members were involved. Open-source solutions were also researched for timetable management. |
Requirements Analysis | Q2: Were stakeholders such as faculty, students, or admin staff involved during the planning stage? | Javid Hussain | Yes, faculty members, IT faculty, and an intern were involved. |
Requirements Analysis | Q2: Were stakeholders such as faculty, students, or admin staff involved during the planning stage? | Tahawur Abbas | Yes, students and admins were involved in planning. |
Requirements Analysis | Q2: Were stakeholders such as faculty, students, or admin staff involved during the planning stage? | Amjad | Yes, feedback from faculty and students was continuously gathered and integrated. |
Requirements Analysis | Q2: Were stakeholders such as faculty, students, or admin staff involved during the planning stage? | Asad Ali | Yes, faculty members and students' requirements were considered during planning. |
Requirements Analysis | Q2: Were stakeholders such as faculty, students, or admin staff involved during the planning stage? | Muhammad Askari | Yes, faculty and IT staff were involved throughout the planning stage. |
Requirements Analysis | Q3: Were there any documented functional and non-functional requirements? Can we see them? | Imtiaz Ahmed | No - formal requirement documents are not available. Documentation will be prepared for new features as the system migrates to an API-based CMS. |
Requirements Analysis | Q3: Were there any documented functional and non-functional requirements? Can we see them? | Javid Hussain | No formal documentation exists; requirements were captured through discussions. |
Requirements Analysis | Q3: Were there any documented functional and non-functional requirements? Can we see them? | Tahawur Abbas | Limited documentation exists; requirements were primarily captured verbally and via meeting notes. |
Requirements Analysis | Q3: Were there any documented functional and non-functional requirements? Can we see them? | Amjad | Thorough documentation was maintained throughout the project's lifecycle. |
Requirements Analysis | Q3: Were there any documented functional and non-functional requirements? Can we see them? | Asad Ali | No, there is no formal documentation. |
Requirements Analysis | Q3: Were there any documented functional and non-functional requirements? Can we see them? | Muhammad Askari | No comprehensive SRS document was created; requirements were tracked informally. |
Requirements Analysis | Q4: What challenges were faced during requirement collection? | Imtiaz Ahmed | Multiple challenges were encountered during requirement collection. |
Requirements Analysis | Q4: What challenges were faced during requirement collection? | Javid Hussain | Many users had limited computer experience; training sessions were conducted to mitigate this. |
Requirements Analysis | Q4: What challenges were faced during requirement collection? | Tahawur Abbas | Lack of clarity in requirements, departmental needs not fully captured, and limited time for planning were key challenges. |
Requirements Analysis | Q4: What challenges were faced during requirement collection? | Amjad | Absence of a formal team leader and limited development time posed challenges. |
Requirements Analysis | Q4: What challenges were faced during requirement collection? | Asad Ali | Various challenges were faced that required logical handling during requirement collection. |
Requirements Analysis | Q4: What challenges were faced during requirement collection? | Muhammad Askari | Challenges arose in tracking requirements and managing scope due to lack of formal documentation. |
Requirements Analysis | Q5: How were conflicting requirements between departments handled during planning? | Imtiaz Ahmed | Reconciliation issues (especially with accounts) were addressed using API-based solutions. |
Requirements Analysis | Q5: How were conflicting requirements between departments handled during planning? | Javid Hussain | Conflicting requirements were managed through informal discussions with faculty and IT staff. |
Requirements Analysis | Q5: How were conflicting requirements between departments handled during planning? | Tahawur Abbas | Conflicting requirements were resolved through discussions between students, admins, and IT team. |
Requirements Analysis | Q5: How were conflicting requirements between departments handled during planning? | Amjad | Conflicts were handled by prioritizing critical features and implementing iterative improvements. |
Requirements Analysis | Q5: How were conflicting requirements between departments handled during planning? | Asad Ali | Conflicts were discussed informally and resolved logically during planning. |
Requirements Analysis | Q5: How were conflicting requirements between departments handled during planning? | Muhammad Askari | Conflicts were difficult to resolve due to absence of a comprehensive SRS document. |
Requirements Analysis | Q6: Were any industry standards or educational guidelines considered during requirement definition? | Imtiaz Ahmed | Yes - industry practices such as object-oriented principles and a concurrent/agile approach were followed. |
Requirements Analysis | Q6: Were any industry standards or educational guidelines considered during requirement definition? | Javid Hussain | Some standard practices like structured PHP and modular development were considered. |
Requirements Analysis | Q6: Were any industry standards or educational guidelines considered during requirement definition? | Tahawur Abbas | Basic coding and design guidelines were applied in line with academic standards. |
Requirements Analysis | Q6: Were any industry standards or educational guidelines considered during requirement definition? | Amjad | Some industry practices and coding standards were informally applied. |
Requirements Analysis | Q6: Were any industry standards or educational guidelines considered during requirement definition? | Asad Ali | No specific guidelines were followed; it was an in-house approach. |
Requirements Analysis | Q6: Were any industry standards or educational guidelines considered during requirement definition? | Muhammad Askari | Industry standards were considered informally during development. |
Requirements Analysis | Q7: Is there a process in place for updating requirements when user needs evolve? | Imtiaz Ahmed | No formal process is documented; updates are handled informally. |
Requirements Analysis | Q7: Is there a process in place for updating requirements when user needs evolve? | Javid Hussain | New students were included as interns in subsequent iterations to assist in further development. |
Requirements Analysis | Q7: Is there a process in place for updating requirements when user needs evolve? | Tahawur Abbas | Updates were applied when user requirements changed or issues arose. |
Requirements Analysis | Q7: Is there a process in place for updating requirements when user needs evolve? | Amjad | Regular updates and version control were used to accommodate evolving requirements. |
Requirements Analysis | Q7: Is there a process in place for updating requirements when user needs evolve? | Asad Ali | Requirements are dynamic and evolve based on changing needs. |
Requirements Analysis | Q7: Is there a process in place for updating requirements when user needs evolve? | Muhammad Askari | Handled informally through stakeholder meetings and incremental development. |
Design & Architecture | Q1: Was any formal software design used (e.g., UML diagrams, ER diagrams)? | Imtiaz Ahmed | There was no formal design initially because Dr. Irshad Hussain, being an expert, directly guided the system design. |
Design & Architecture | Q1: Was any formal software design used (e.g., UML diagrams, ER diagrams)? | Javid Hussain | No formal design tools; Joomla and structured PHP were used. |
Design & Architecture | Q1: Was any formal software design used (e.g., UML diagrams, ER diagrams)? | Tahawur Abbas | Yes, an ER diagram was created for database structure. |
Design & Architecture | Q1: Was any formal software design used (e.g., UML diagrams, ER diagrams)? | Amjad | Yes, an ER diagram was developed. |
Design & Architecture | Q1: Was any formal software design used (e.g., UML diagrams, ER diagrams)? | Asad Ali | Basic system design was used, but no formal diagrams were created. |
Design & Architecture | Q1: Was any formal software design used (e.g., UML diagrams, ER diagrams)? | Muhammad Askari | ER diagrams were used for database design. No UML diagrams were created. |
Design & Architecture | Q2: Were design alternatives evaluated before implementation? | Imtiaz Ahmed | No - design alternatives were not formally documented. |
Design & Architecture | Q2: Were design alternatives evaluated before implementation? | Javid Hussain | Yes, design alternatives were considered informally based on feasibility and system requirements. |
Design & Architecture | Q2: Were design alternatives evaluated before implementation? | Tahawur Abbas | Yes, the design was evaluated. |
Design & Architecture | Q2: Were design alternatives evaluated before implementation? | Amjad | Yes, discussions were held to address system limitations and the choice of PHP. |
Design & Architecture | Q2: Were design alternatives evaluated before implementation? | Asad Ali | Yes, design alternatives were informally discussed among team members. |
Design & Architecture | Q2: Were design alternatives evaluated before implementation? | Muhammad Askari | Yes, design alternatives were evaluated with stakeholder approval. |
Design & Architecture | Q3: Was the design reviewed or approved by stakeholders? | Imtiaz Ahmed | Yes, Dr. Irshad Hussain reviewed the design. |
Design & Architecture | Q3: Was the design reviewed or approved by stakeholders? | Javid Hussain | Yes, Dr. Irshad Hussain supervised development and reviewed code. |
Design & Architecture | Q3: Was the design reviewed or approved by stakeholders? | Tahawur Abbas | The design was reviewed internally but not formally approved by external stakeholders. |
Design & Architecture | Q3: Was the design reviewed or approved by stakeholders? | Amjad | Yes, the design was reviewed and approved by key stakeholders. |
Design & Architecture | Q3: Was the design reviewed or approved by stakeholders? | Asad Ali | Yes, stakeholders were consulted informally. |
Design & Architecture | Q3: Was the design reviewed or approved by stakeholders? | Muhammad Askari | Yes, stakeholders approved design alternatives. |
Design & Architecture | Q4: What architecture pattern is the LMS based on? (Monolithic, Microservices, Layered, etc.) | Imtiaz Ahmed | The system uses a layered approach typical for Joomla-based applications. |
Design & Architecture | Q4: What architecture pattern is the LMS based on? (Monolithic, Microservices, Layered, etc.) | Javid Hussain | A structured, layered approach. |
Design & Architecture | Q4: What architecture pattern is the LMS based on? (Monolithic, Microservices, Layered, etc.) | Tahawur Abbas | Layered architecture was applied within the limitations of Joomla. |
Design & Architecture | Q4: What architecture pattern is the LMS based on? (Monolithic, Microservices, Layered, etc.) | Amjad | Layered/monolithic approach was used; modular separation maintained. |
Design & Architecture | Q4: What architecture pattern is the LMS based on? (Monolithic, Microservices, Layered, etc.) | Asad Ali | Layered architecture was informally applied. |
Design & Architecture | Q4: What architecture pattern is the LMS based on? (Monolithic, Microservices, Layered, etc.) | Muhammad Askari | The system follows a microservices architecture. |
Design & Architecture | Q5: How do you manage scalability and modularity in the system? | Imtiaz Ahmed | Through Joomla features, scalability and modularity are managed. |
Design & Architecture | Q5: How do you manage scalability and modularity in the system? | Javid Hussain | Scalability and modularity are managed within the structured layered system. |
Design & Architecture | Q5: How do you manage scalability and modularity in the system? | Tahawur Abbas | Scalability and modularity were difficult to manage. |
Design & Architecture | Q5: How do you manage scalability and modularity in the system? | Amjad | Modular separation was maintained for clarity and maintainability; plans to shift from Joomla to Laravel to improve scalability. |
Design & Architecture | Q5: How do you manage scalability and modularity in the system? | Asad Ali | Basic modularity is maintained; scalability is planned for future upgrades. |
Design & Architecture | Q5: How do you manage scalability and modularity in the system? | Muhammad Askari | Scalability and modularity were achieved through microservices architecture. |
Design & Architecture | Q6: Do you have any plans to make the website more secure, such as by adding features like an SSL certificate? | Imtiaz Ahmed | Yes - an SSL certificate is already in place for the website but not for LMS. |
Design & Architecture | Q6: Do you have any plans to make the website more secure, such as by adding features like an SSL certificate? | Javid Hussain | Security measures like query sanitization and XSS protection were implemented early; SSL implementation is planned. |
Design & Architecture | Q6: Do you have any plans to make the website more secure, such as by adding features like an SSL certificate? | Tahawur Abbas | Yes, security measures like SSL certificates were considered. |
Design & Architecture | Q6: Do you have any plans to make the website more secure, such as by adding features like an SSL certificate? | Amjad | Yes, SSL certificate implementation was planned (already purchased). |
Design & Architecture | Q6: Do you have any plans to make the website more secure, such as by adding features like an SSL certificate? | Asad Ali | For website security, SSL and VHE are applied; LMS security is planned. |
Design & Architecture | Q6: Do you have any plans to make the website more secure, such as by adding features like an SSL certificate? | Muhammad Askari | SSL and security improvements are planned for LMS. |
Design & Architecture | Q7: Was the database schema designed for flexibility and future growth? | Imtiaz Ahmed | The database schema allows basic growth; ER diagrams guided design. |
Design & Architecture | Q7: Was the database schema designed for flexibility and future growth? | Javid Hussain | The database was structured for current requirements, but flexibility was limited. |
Design & Architecture | Q7: Was the database schema designed for flexibility and future growth? | Tahawur Abbas | ER diagram-based schema allows for some future growth. |
Design & Architecture | Q7: Was the database schema designed for flexibility and future growth? | Amjad | The database design is modular and adaptable for future enhancements. |
Design & Architecture | Q7: Was the database schema designed for flexibility and future growth? | Asad Ali | Database designed for current needs with some modularity for future updates. |
Design & Architecture | Q7: Was the database schema designed for flexibility and future growth? | Muhammad Askari | Yes, ER diagrams were used for database schema design. |
Design & Architecture | Q8: Are there separate layers for business logic, data access, and presentation in the system? | Imtiaz Ahmed | Yes, Joomla's built-in structure provides basic separation of concerns. |
Design & Architecture | Q8: Are there separate layers for business logic, data access, and presentation in the system? | Javid Hussain | Yes, structured layered approach. |
Design & Architecture | Q8: Are there separate layers for business logic, data access, and presentation in the system? | Tahawur Abbas | Basic separation is followed between database access and application logic. |
Design & Architecture | Q8: Are there separate layers for business logic, data access, and presentation in the system? | Amjad | Yes, modular separation was maintained. |
Design & Architecture | Q8: Are there separate layers for business logic, data access, and presentation in the system? | Asad Ali | Layers exist informally within the Joomla structure. |
Design & Architecture | Q8: Are there separate layers for business logic, data access, and presentation in the system? | Muhammad Askari | Yes, business logic, data access, and presentation layers are separated using microservices principles. |
Design & Architecture | Q9: Is the system designed to support integration with third-party platforms (e.g., payment gateways, learning tools)? | Imtiaz Ahmed | Currently, no third-party platform support is implemented. |
Design & Architecture | Q9: Is the system designed to support integration with third-party platforms (e.g., payment gateways, learning tools)? | Javid Hussain | No, system follows a structured approach without third-party plugins. |
Design & Architecture | Q9: Is the system designed to support integration with third-party platforms (e.g., payment gateways, learning tools)? | Tahawur Abbas | System designed for potential integration but not implemented yet. |
Design & Architecture | Q9: Is the system designed to support integration with third-party platforms (e.g., payment gateways, learning tools)? | Amjad | Third-party integrations are possible with additional development. |
Design & Architecture | Q9: Is the system designed to support integration with third-party platforms (e.g., payment gateways, learning tools)? | Asad Ali | Planned for future LMS updates; not currently implemented. |
Design & Architecture | Q9: Is the system designed to support integration with third-party platforms (e.g., payment gateways, learning tools)? | Muhammad Askari | Integration support is considered but not yet implemented. |
Development Process | Q1: What programming languages or frameworks were used at the beginning of the development process? | Imtiaz Ahmed | Joomla was used initially. |
Development Process | Q1: What programming languages or frameworks were used at the beginning of the development process? | Javid Hussain | Backend: PHP (structured); Database: SQL. |
Development Process | Q1: What programming languages or frameworks were used at the beginning of the development process? | Tahawur Abbas | Core PHP and Joomla were used for backend. |
Development Process | Q1: What programming languages or frameworks were used at the beginning of the development process? | Amjad | PHP and Joomla. |
End of preview. Expand in Data Studio
README.md exists but content is empty.
- Downloads last month
- 10