Assignments

Assignments Required documents Deadline

Assignment 1 Problem: X-rental source code Week7 (FRI)
Deployment on Azure/AWS (4 points)
- Deploy system from code, create installation guide
(3 points)
- Update code for BE and FE to be able to work
together (1 points)
Descript the system (5 points)
- Give overview of system (1 points)
- Give suggestion for GUI design (1 point)
- Create database structure (1 point)
- Create component diagram (2 points)
Extra point (1 points): issues in code
Assignment 2 Understanding problem (2 points) Week9 (FRI)
- Constraints
- Needed quality attributes
- Conceptual diagram
- Use cases / CRC cards
Create WBS – work breakdown structure (1 points)
Building solution (3 points)
- Important Architecture Decisions: eg. the list of
technologies that you will use to build the system
and the reason you choose them
- Component diagram
- Database
Implement solution (3 points)
- Source code
- Deployment diagram
- Deployment / Installation guide
- Complete SAD
Peer Review (1.5 points)
- Review code of other group, give comment and
suggestion for code (0.5 points)
- Review desgin of other group, give comment and
suggestion for design (0.5 points)
- Deploy system from code, give comments for
installation guide (0.5 points)
Another requirement:
- Document naming: <group_name>_<File_name>_<version_number>.docx
- Using git flow for controlling both source code and document
List of problems for assignment 2
Problem 1: Sonoma project
Problem 2: Data crawling - recruiment data in HCMC

Sonoma project
Files to import (and to be discussed on if need)
• 2a YSI raw data uncleaned All 18 Oct 2018 to 25 March 2021.csv
• 2b DRAFT Sonoma Watershed Summer 2020 Water Temperature_20210217.xlsx
• 2c raw data VuSitu_20190403_to_20190502_So07 Yulupa at the
bridge_Log_WY2018.xlsx
• 3 DRAFT Editing Copy YSI All 25 Jan 2018 to 31 Aug 2020_LastEdit_20210208_ example
for Mark Flocco.xlsx
• 4 DRAFT Rating_Curve_Data_ALL_20210519_wh_graphing.xlsx
• 5 GSA Seepage Single Site Data Sheet.xlsx
• 6a GSA Seepage 18 site short run 2021_01_Gain_Loss_Analysis__wQ1K_WIP.xlsx
• 6b GSA Seepage 55 site full run 2021_03_Gain_Loss_Analysis_wQ1K_WIP_V2.xlsx
• 7 PRMD SEC Pathogens Results 7-15-19_WH_eds_31July2019.xlsx
• 8 Aquatic Insect_BMI_Sonoma_Creek_Watershed_by_site_2012.xlsx

Summary
The Sonoma Ecology Center (SEC) is a nonprofit serving the ecological health of the greater
Sonoma Valley area. Over more than 30 years of its existence, SEC has undertaken projects
which have accumulated data. These data have been, to date, stored in multiple spreadsheets.
Due to the fragmented nature of the spreadsheets, there is an obvious benefit to consolidating
this data for future analysis and reference.
SEC undertakes research projects developed both from within the organization and under
contract from other entities, such as the State of California. In the latter case, the contract will
frequently require data or reporting deliverables in various formats. However, in all cases, there
is a clear benefit to the ability to create various types of reports and/or visualizations.

Goals and Scope

• Consolidate historical project data into a central database
• Enable straightforward entry of future project (and other) data into database
• Provide “simple” reporting front end with visualizations
• Provide ability to export data into multiple deliverable formats

Data Types
Existing data types are likely, but not guaranteed, to reflect future needs. Most are time series
recordings of measurements at specific locations. Examples include:
• Streamflow data
• Water quality or other meter logged data
• Habitat, plant, or animal species data (numbers, sizes, quality) • Environmental/weather
readings
• Wildlife camera data (linking to images and video)
• Site photos taken at reading locations
• Reach data: Calculated measurements between two data points. For instance, streamflow
changes between point A and B. Some calculations may be more complex.

Extensibility
Because future projects are likely but not guaranteed to follow similar time series/location
based formats, the database architecture should prioritize this type of data while allowing for
flexible extensibility. The user interface should also be extensible in that it should allow for the
addition of fields or tables when creating new projects or adding to existing projects. SEC does
not employ a database professional and contracts out most higher level IT work. This should be
an important consideration in the design and function of the database.

Interface
The user interface should be browser based and capable of multiple functions:
• Simple data entry
• Data import (from CSV)
• Configuration of report types
• Report generation
• Deliverable exports (often but not always CSV)
• Simplified database administration (adding tables and fields, for instance)
• Visualizations
In addition to the browser-based user interface, a longer term goal of the project is to plot the
database information on a public-facing map so that the community at large has access to a
subset of the data.

Crawling requirements
Websites to crawl
Web page: https://www.topcv.vn/
Web page: https://www.vietnamworks.com/
Web page: https://timviec365.vn/
Web page: https://careerbuilder.vn/
Web page: https://123job.vn
Web page: https://topdev.vn/

Summary
The Recruitment Hub is a multi-vertical recruitment agency covering all sectors and disciplines
across the permanent, temporary, and interim arenas. We are focussing now on providing
recruitment services. To do so, we will be riching our data of recruitment into the ASIA area and
we will continue to provide an exemplary recruitment process to our candidates and clients,
putting them at the heart of everything we do.

Goals and Scope

• Enable to crawl recruitment information and organize it into a database
• Enable to schedule spiders to crawl recruitment information from webs
• Enable to manage & control spiders
• Provide “simple” reporting front end with visualizations
• Provide ability to export data into multiple deliverable formats

Data Types
There is no requirement about data type, except that the data must be structured and
organized to be easy for analyzing purpose

Extensibility
Because future projects are likely but not guaranteed to follow similar formats, the database
architecture should prioritize this type of data while allowing for flexible extensibility. The user
interface should also be extensible in that it should allow for the addition of new spiders.

Interface
The user interface should be browser based and capable of multiple functions:
• Simple UI for managing and controlling spiders
• Notify when there is any stuck with crawling such as web site does not allow crawling, web’
structure has been changed to be able to update spiders if need
• Configuration of report types
• Report generation
• Deliverable exports (CSV, excel and pdf)
• Simplified database administration (adding tables and fields, for instance)
• Visualizations