CSSML
CSSML
● Phishing Database:
● Algorithm Documentation:
● Comprehensive documentation to help users install and use the tool effectively.
● To achieve these deliverables, the following activities will be executed:
● Research and Requirements Analysis: Study phishing tactics and review current
detection tools.
●Web App Development: Complete the web app’s frontend and backend.
● Project Manager: Oversees the project, coordinates tasks, and ensures milestones
are achieved.
● Developers: Focus on backend and frontend development for the tool, ensuring
robust and user-friendly functionality.
● Quality Assurance (QA): Conducts testing to confirm the tool’s reliability and
accuracy.
● Each role is assigned specific activities and expected deliverables within the project’s timeline:
● Project Manager (Amanuel Tsehay): Oversees planning, manages timelines, and ensures team
members remain aligned with project goals.
● Backend Developer (Obsu Kebede) Develops backend systems for processing phishing
detections and integrates algorithms into the application.
● Frontend Developer (Daniel Asrat): Designs and implements the web interface or browser
extension.
● Database Manager (Bikila Tariku): Gathers and maintains datasets, ensures database updates,
and manages data access for real-time detection.
● UI/UX Designer (Feven Lendu): Designs the user interface, focusing on ease of use and
navigation.
● Quality Assurance (Biruk Amanuel): Tests the system for reliability, compatibility, and
accuracy, ensuring the tool’s quality and functionality.
● Resources are distributed to support a balanced workload and ensure that each project
phase receives the necessary attention. Weekly hours for each member are assigned
based on their expertise and tasks in the development lifecycle:
● Personnel Allocation: Weekly hours for each team member range between 20 to 30,
with roles assigned based on individual expertise.
● Time Allocation: Resources are dedicated to stages like data collection, algorithm
development, interface design, and testing to maintain steady progress toward
milestones.
●The team uses a structured communication plan to ensure transparency,
accountability, and timely decision-making:
●Client Updates: Weekly progress emails to inform the client and supervisor,
with monthly check-in meetings to review milestones and receive feedback
●To structure the project, specific activities, dependencies, and milestones are
identified:
● Risk Control Measures: Procedures are established for dataset availability, team availability, and
technical issues, with contingency plans for reassigning tasks if necessary.
● Progress Monitoring: Project management tools such as Trello or Asana track progress and
manage dependencies, ensuring transparency and the ability to adjust schedules as needed.
● By maintaining this organized structure, the team can effectively manage tasks, reduce risks,
and deliver a high-quality phishing detection tool aligned with client expectations and project
goals.
Management Targets
● Successfully deliver a functional phishing detection tool as both a browser extension and a web-based application.
● Ensure that each development phase is completed within the specified timeline and with high quality.
● Achieve a detection accuracy rate that meets or exceeds the client’s expectations and passes predefined tests.
● Facilitate effective communication and collaboration within the team and with stakeholders through regular updates and
progress reports.
●Assumptions include access to reliable phishing datasets (e.g., PhishTank),
availability of team members as per the project timeline, and access to
required resources (e.g., development tools, testing platforms).
●The project’s success depends on the availability of comprehensive datasets
for training and testing the machine learning model, as well as timely
feedback from the client and supervisors on prototype iterations.
● Data Access and Quality: If datasets like PhishTank are unavailable or
insufficient, we may need to gather additional data or rely on alternative
sources, which could delay training.
●Algorithm Performance: The phishing detection model may not achieve high
accuracy initially. To mitigate this, we will conduct thorough testing and
model refinement.
●Data Sources: PhishTank and other open-source datasets will provide data for
training and validation. Web scraping tools may supplement this data if
●Version Control: Git will be used for code versioning, with frequent commits
and team code reviews.
● Objectives: The documentation plan ensures clarity and consistency across all
project-related documents, making it easier for team members and stakeholders to
understand project progress and outcomes.
● Document Style and Attributes: All documents will follow a consistent style, with
clear headings, sections, and a template specifying the author(s), date, and document
status (draft, review, final). Each document will include a version history detailing
changes, with appropriate comments by reviewers.
● The project is organized into several key work packages and sub-projects, each with distinct
deliverables. The Research and Data Gathering phase involves conducting a thorough investigation
into phishing tactics and collecting datasets of known phishing websites. This phase will produce a
comprehensive research report and a cleaned dataset for use in subsequent stages.
● In the Frontend and Backend Development stage, an intuitive user interface for either a web
application or browser extension will be developed alongside backend functionality to handle website
analysis.The Database Management phase will ensure the tool has a continuously updated database
ophishing websites, maintained in real-time. Next, Testing and Quality Assurance will involve rigorous
evaluation of the tool’s detection accuracy, with the results compiled in a testing and security report.
Finally, the Deployment and Maintenance
Communication Plan
● · Weekly Progress Updates: Brief email updates sent to the client and supervisor.
● · Monthly Check-In Meetings: Virtual or in-person meetings to discuss milestones and receive
feedback.
● 2. Final Presentation: Organized event for demonstrating the completed tool, inviting relevant
stakeholders.