The lab assignments can be found on the Jones and Bartlett site. Everything that you need is on the site. To login,

1. Go to link of the lab within this module
2. If you have not registered your account and activated your code, please read the instructions under the Getting Started module
3. Log into the site using your account
4. Select the labs for this course
5. Select the appropriate lab for this unit

You do not have to complete a lab in one sitting. The lab will keep track of your progress and if you save before exiting, the environment will save your progress to that point.

Please be sure to read the introduction and background material and watch my recording before you get started, as the material sets the stage for the lab.

Take your time on the labs and follow the steps closely. The lab will take you step-by-step through the process. Please note that the labs are a “sandbox” environment, so you can always reset the lab if you get too far off track. If you run into any technical support issues, you can reach out directly to tech support from within the lab.

The entire lab report will be created within the Jones and Bartlett system, including the needed screenshot. Be sure to watch the Lab Tutorial video below to get started or if you have any questions about working with the labs.

Once you have completed the lab, download the lab report PDF and submit it here.

Below are some videos to help with submitting assignments in the lab:

1. Kapan Proklamasi Kemerdekaan Republik Indonesia terjadi dan siapa saja yang membacanya?

Assignment due Friday, March 6, 2026 by 11:59pm

Interactive Computer Vision Tool with GUI

Submission: PDF documentation (Primary resource) + .py script + demo video link

Objective

Design and implement a standalone desktop computer vision tool using OpenCV and Tkinter. The tool must provide a graphical user interface (GUI) that allows users to open a local image or access the webcam, apply image processing and vision operations,** adjust parameters interactively**, and save the output. The emphasis is on correct implementation, usability, parameter control, and clear documentation.

Functional Requirements (What your tool must do)

A. Input & I/O

Open Local Image

i) File Open (Tkinter menu), ii) Supported formats: JPG, PNG, BMP (at least)

Access Live Webcam

i) File Access Live Webcam, ii) Display live feed in the main window, iii) Take Snapshot button to freeze a frame and switch to static-image mode

Save Output

i) File Save As, ii) Save the currently displayed image (processed result)

B. GUI & Interaction

Implement** at least** the following GUI features:

• Menu bar (File / Tools)
• Buttons (e.g., Apply, Snapshot)
• Trackbars / sliders for real-time parameter control
• Text box for numeric input (with validation)
• Clean exit and proper resource release (camera, windows)

C. Image Processing & Vision Operations (Choose 10 total, with constraints)

You must implement at least 10 operations overall, satisfying the minimum coverage below. You may implement more for bonus credit.

1. Foundations & Color (Choose 2)

• RGB channel access and manipulation
• Grayscale conversion
• Brightness / contrast adjustment
• HSV (Hue/Saturation/Intensity) adjustment
• Color blindness simulation (matrix-based)

2. Image Statistics (Implement all)

• Histogram computation and display
• Histogram equalization

3. Point & Local Operators (Choose 2)

• Contrast stretching
• Median filter (kernel size via text box)
• Gaussian smoothing (kernel size + )
• Sharpening (Laplacian or custom kernels)

4. Edge Detection (Choose 2)

-** Sobel** (kernel size + threshold defined as a ratio of mean)

• Canny (control t1, t2, aperture size)
• Laplacian of Gaussian (LoG) (, kernel size, threshold)

5. Segmentation (Choose 2)

• Global thresholding
• Adaptive thresholding (block size, method, etc.)
• Contour detection
• OR one advanced method:
  • Mean Shift (sp, sr, pyramid levels)
  • Superpixels (SLIC: n_segments, compactness)

Implementation Rules:

##** i) Python only, **

##** ii) OpenCV + Tkinter only (no PyQt, no web frameworks)**

##** iii) Must run locally (not Colab), your tool will be tested by the instructor via calling your script from terminal **

• AI tools may be used, but **you must understand and explain your code in the technical interview **
• Code must be well-structured (functions/classes, not one giant script)

Your tool should handle edge cases (such as no image loaded, invalid parameters). These should not cause a crash; instead, the user should be informed (for example: Please load an image before running the function) ) and when necessary parameter values should be set to default (when they are set outside of acceptable ranges (e.g. kernel size = -1))

Deliverables:

IMPORTANT: In your submission, you should upload the PDF as primary resource and a zip file containing both the PDF and the script as a secondary resource.

1.** PDF Documentation (36 pages): Primary resource to upload**

Your PDF must include:

• **Overview of the Tool **
  • A short description of the main features of the tool
• **List of Implemented Functionalities **
  • One subsection per operation
• **Parameters Table **
  • For each operation:
    • Parameter name
    • Type (slider/textbox/menu)
    • Valid range
    • Effect on output
• **GUI Screenshots **
  • Annotated where appropriate

2. Python Script (****.py**): To pack together with the PDF file and upload as a secondary resource **

Your script must:

• Launch the GUI
• Support image and webcam modes
• Provide interactive controls for selected operations
• Save outputs correctly
• Be readable and commented

**File name example: **cv_gui_assignment1_.py

3. Video Demonstration (24 minutes): To include in the first page of the PDF

Include** link** (Google Drive) in your PDF (at the beginning of the) document showing the following user operations:

• Opening an image
• Using **at least 4 different operations **
• Adjusting parameters live
• Accessing webcam and taking a snapshot
• Saving the output

Bonus (Optional)

• Side-by-side original vs processed view
• Preset buttons (e.g., Low Noise, Strong Edges)
• Keyboard shortcuts

Academic Integrity

This is an individual assignment. You may discuss ideas, but code and documentation must be your own. Any AI-assisted code must be understood and defensible during evaluation.

If this description overwhelmed you, consider doing the following list of first (sample implementation for task11 is available ).

Assignment Information

Weight:

15%

Learning Outcomes Added

• : Describe the foundation of image formation and image processing.
• : Compare various computer vision methods used for feature detection, edge computation, motion estimation, reconstruction, and recognition.

Time-Series Forecasting with Gaussian Processes

Example Dataset:

Assignment Overview:

Students will use Gaussian Processes to model and forecast time-series data, such as stock prices or weather data. The goal is to understand how Gaussian Processes provide probabilistic predictions and quantify uncertainty.

Assignment Instructions:

1. Data Collection: Obtain a time-series dataset, such as historical stock prices or temperature readings.
2. Preprocessing: Preprocess the data by handling missing values, normalizing the data, and splitting it into training and testing sets.
3. Model Implementation: Implement a Gaussian Process model using Python and the GPyTorch library. Define an appropriate kernel function and set up the model for regression.
4. Training: Train the Gaussian Process model on the training dataset, optimizing the kernel parameters.
5. Forecasting: Use the trained model to forecast future values of the time-series data, generating probabilistic predictions.
6. Evaluation: Evaluate the model’s performance by comparing the forecasted values with the actual values in the testing dataset, using metrics such as mean squared error and log likelihood.
7. Reporting: Write a report detailing the methodology, results, and insights gained from the assignment, adhering to the Gaussian Processes Assignment Rubric.

Submission Instructions:

Report (.pdf or .docx format):

• Clearly explain your:
• Dataset choice and characteristics.
• Preprocessing steps.
• Model design (kernel choice, hyperparameters, etc.).
• Training process and forecasting method.
• Evaluation results (MSE, log-likelihood, etc.).
• Interpretation of uncertainty and confidence intervals.
• Follow the structure and criteria outlined in the rubric.

Assignment due Thursday, March 5, 2026 by 11:59pm

ICS 432 Software Engineering

Assignment 1: Designing a Secure Financial Trading Platform

Integration of Software Engineering Principles, Design Patterns, and Best Practices

Objective

Design a prototype for a Financial Trading Platform that addresses real-world challenges, adheres to industry standards, and demonstrates mastery of software engineering principles.

Instructions

Part 1: Real-World System Requirements & Prioritization (25 points)

1.** Critical System Considerations** (Refer to Week 2 Lecture 1: Requirements Gathering in Finance): – Identify 5 critical considerations (e.g., regulatory compliance, data integrity, scalability) for building a financial trading platform. – Hint: For each consideration:

Explain its importance (e.g., “Regulatory compliance ensures adherence to laws like SEC rules to avoid legal penalties”).

Describe how you would implement it (e.g., “Use automated audit trails for compliance tracking”).

1. Agile Prioritization (Refer to Week 2 Lecture 2: Prioritizing Features):
   • Use the MoSCoW method to categorize the following features:

Real-time market data feeds

Two-factor authentication (2FA)

Portfolio and Account Management

Customizable Dashboards and Themes

Order Management

Automated fraud detection

High-frequency trading support

Social trading integration

- Justify your categorization (e.g., "Automated fraud detection is a **Must-have** to comply with anti-money laundering regulations").

Part 2: System Design & Architecture (30 points)

1.** SOLID Principles** (Refer to Week 3 LP1: SOLID Principles): – A class TradeProcessor handles order validation, execution, logging, and notifications.

Identify 2+ SOLID violations (e.g., SRP violation due to multiple responsibilities).

Redesign the system into modular classes (e.g., OrderValidator, TradeExecutor, AuditLogger).

1. Design Patterns (Refer to Week 3 LP3: Creational Patterns and Week 4 LP1/LP3: Structural/Behavioral Patterns):
   • Creational: Use the Factory Method Pattern to create different order types (e.g., MarketOrder, LimitOrder).
   • Structural: Apply the Adapter Pattern to integrate a legacy risk assessment module into your modern system.
   • Behavioral: Implement the Observer Pattern to notify users when stock prices hit predefined thresholds (e.g., email/SMS alerts).
2. SDLC Alignment (Refer to LP3: SDLC & Best Practices):
   • Map your design to the SDLC phases:

Requirements: How did stakeholder interviews shape your design?

Testing: How will stress testing ensure performance during market volatility?

Part 3: Implementation & Security (30 points)

1.** Code Development** (Refer to Week 4 LP3: Behavioral Patterns): – Write a Python snippet for the Command Pattern to enable undo/redo functionality for trade cancellations. – Implement the Proxy Pattern to rate-limit API requests (e.g., 100 requests/sec per user).

1. Security & Testing (Refer to LP3: Testing & Security):
   • Propose 2 security measures (e.g., encryption for trade data, input validation) to mitigate risks like SQL injection.
   • Design 3 unit tests for the OrderValidator (e.g., invalid order amounts, duplicate trades).

Part 4: Deployment & Reflection (15 points)

1.** Containerization** (Refer to LP1: Introduction to Software Engineering): – Draft a Dockerfile to containerize your platform, including steps to install dependencies and expose port 8080.

1. Trade-off Analysis (Refer to Week 3 LP3: Creational Patterns):
   • Compare the Singleton Pattern (for managing user sessions) with the Object Pool Pattern. Discuss pros/cons in scalability.
2. Future Improvements (Refer to Week 4 LP3: Behavioral Patterns):
   • Suggest 1 design pattern (e.g., Strategy Pattern for dynamic pricing algorithms) to enhance the platform.

Submission Guidelines

Submit a PDF report (max 10 pages) with:

o UML diagrams for key components (optional).

o The fully commented code adhering to PEP 8 standards.

o Explicit references to pre-class materials (e.g., “The Adapter Pattern aligns with Week 4 LP1 recommendations for integrating legacy systems”).

Due Date: Week 8 of the semester

Grading Rubric

Real-World Analysis: Depth of considerations (25%)

Design Quality: SOLID compliance, pattern correctness (30%)

Implementation: Security rigor, test coverage (30%)

Reflection: Practicality of deployment and future improvements (15%)

Note:

** Where to Refer**:

o** SOLID Principles**: Week 3 LP1 (SOLID in Health Record Systems).

o Design Patterns: Week 3 LP3 (Creational), Week 4 LP1 (Structural), Week 4 LP3 (Behavioral).

o SDLC & Security: LP3 (SDLC phases, testing best practices).

o Containerization: LP1 (Docker setup, environment isolation).

Assignment Information

Length:

3000

Weight:

15%

Learning Outcomes Added

• : Apply security principles throughout the software development lifecycle
• : Examine applicable security principles, ethics, and practices in the domain of software development

Please follow the instructions provided on the attachment, let me know if you have any questions.

This is due today 02/27/2026 at 6pm.

Activity Overview: In this graded activity, students will learn how to publicly host web-content via two alternative methodologies. Students will host a static website directly via storage, and a server-less application.

Activity Outcomes: After completing this activity will be able to

• Demonstrate configuration of storage accounts
• Demonstrate configuration of server-less applications
• Demonstrate web-hosting principles

Deliverable: Upload all requested screenshots below, as a .pdf export from the editor of your choosing.

Naming convention: “lastnamefirstinitial_Activity#.pdf” e.g: “smithp_A1.1.pdf”

Be sure to include your name, student number, and course (CNW-2511) at the top of your document.

Hosting Web Content in Azure

Part of the advantage in hosting an environment on a Cloud platform is the ease of access to resources from anywhere in the world. In order to leverage this advantage, organizations must provide publicly-accessible web content in a highly-available, scalable, yet cost-efficient manner. Technicians must be familiar with many of these deployment models, along with the various methods to implement them.

Utilizing a Command-Line Interface (CLI) is often preferable to a Graphical User Interface (GUI) in a production environment. Provisioning, automation, and configuration become far more efficient when a technician can perform tasks in this way.

Follow this link to log in to the Azure Portal. Virtual Machines (and many other billed resources), must be disabled/deleted via the Azure dashboard to prevent continuous billing. Shutting down a VM within the OS will not disable them.

After you have completed this activity, you will delete all created resources, then verify with screenshots.

Do not create any resources unless you are specifically requested to. This runs a very high risk of your student account credits ($100 cap) being spent in their entirety, at which point you will no longer be able to access any of the resources required for this course, and future courses.

In this lab, you will be provisioning:

• One (1) Resource Group
• One (1) Storage Account
• One (1) Storage Blob
• One (1) App Service Plan
• One (1) App Service

As you progress through this activity, your instructor may request that you capture a screenshot periodically (on Mac OS: “command+shift+3” to capture the whole screen, or “command+shift+4” then drag the cursor over the area you would like to capture). These screenshots are part of your required deliverable and will be graded.

Please attend or view Live Lecture (Week 3 Part 1) when available for the latest walkthrough. It is important to understand Cloud Service Provider (CSP) platforms change frequently, so the available recording here may look differently than what you see. You are welcome to use your best judgement to navigate any differences, or wait until the Live Lecture recording becomes available for further elaboration.

Host a Static Website via Storage

1. Create a new Resource Group
   1. Region: East US 2
   2. Name: CNW-WEB
2. Create a new Storage Account
   1. Resource Group: CNW-WEB
   2. Storage Acct Name: “firstinitiallastname”web
   3. Location: East US 2
   4. Performance: Standard
   5. Account Kind: StorageV2
   6. Replication: Locally Redundant (LRS) or no redundancy, if available
   7. Access-Tier: Standard (Whichever option is least expensive, this is considered Cool storage)
      
3. Create a Static Website from within the Storage Account
   1. In the sidebar, under “Data Management” click “Static Website”
   2. Click “Enabled”
   3. Index Document Name: “index.html”
   4. Note the Primary Endpoint URL (this is the public URL to access your static website)
   5. Access “$web” container and upload “index.html” (download the .zip below and extract)
   6. Leave upload blob setting as their defaults
4. Access your static website via the Endpoint URL (great color, huh!?) – screenshot
5. Return to to “Data Management > Static Website” and click “$web” to access the container
6. Click “Index.html” then select “Edit Blob”
7. On line 19, change the “bgcolor” Hex value to “FFFF00” (yellow) and click “Save” – screenshot
8. Access your website URL to see the changes (you may need to reload a few times)

• 1 KB

Host a Website via Server-less App

1. Create an App Service Plan
   1. Name: “firstinitiallastname“web
   2. Resource Group: CNW-WEB
   3. OS: Windows
   4. Location: Central US
   5. Pricing Tier: F1 Free
2. Create an App Service
   1. Name: cnw1″firstinitiallastname“
   2. Resource Group: CNW-WEB
   3. App Service Plan: The plan you just created (should be selected by default)
   4. Application Insights: Disabled
   5. OS: Windows
   6. Runtime Stack: .NET Core 2.1 (or the nearest version if 2.1 is not available)
3. Configure App Service to display static website
   1. Navigate to your storage blob website
   2. Right click on the page, and select “View Page Source”
   3. Select all (cmd+a), then copy (cmd+c)
   4. Navigate back to your App Service
   5. In the sidebar, select “Development Tools > App Service Editor”
   6. Click “Go”
   7. Select “WWWROOT > hostingstart.html”
   8. Select all (cmd+a), then paste the copied html from step C
   9. On line 19 or 20, change the “bgcolor” hex value to “F00200” (red)
   10. Navigate to the App Service’s public URL (which can be found on the overview page) – it should be “cnw1firstinitallastname.azurewebsites.net”

Required Screenshots

The following screenshots should show the configurations identified in lab, for each component:

1. Storage Account
   1. Overview page
   2. Static Website page
2. Browser displaying the blob-hosted website (purple) – be sure to capture the entire browser window
3. Browser displaying the blob-hosted website (yellow) – be sure to capture the entire browser window.
4. App Service Plan Overview page
5. App Services
   1. Overview page
   2. App Services Editor displaying HTML for the hosted website
6. Browser displaying the App Services-hosted website (red) – be sure to capture the entire browser window
7. All Resources page showing that all resources have been completely deleted (it should be empty)

There should be 9 individual screenshots.

Activity Overview: In this graded activity, students will learn how to publicly host web-content via two alternative methodologies. Students will host a static website directly via storage, and a server-less application.

Activity Outcomes: After completing this activity will be able to

• Demonstrate configuration of storage accounts
• Demonstrate configuration of server-less applications
• Demonstrate web-hosting principles

Deliverable: Upload all requested screenshots below, as a .pdf export from the editor of your choosing.

Naming convention: “lastnamefirstinitial_Activity#.pdf” e.g: “smithp_A1.1.pdf”

Be sure to include your name, student number, and course (CNW-2511) at the top of your document.

Hosting Web Content in Azure

Part of the advantage in hosting an environment on a Cloud platform is the ease of access to resources from anywhere in the world. In order to leverage this advantage, organizations must provide publicly-accessible web content in a highly-available, scalable, yet cost-efficient manner. Technicians must be familiar with many of these deployment models, along with the various methods to implement them.

Utilizing a Command-Line Interface (CLI) is often preferable to a Graphical User Interface (GUI) in a production environment. Provisioning, automation, and configuration become far more efficient when a technician can perform tasks in this way.

Follow this link to log in to the Azure Portal. Virtual Machines (and many other billed resources), must be disabled/deleted via the Azure dashboard to prevent continuous billing. Shutting down a VM within the OS will not disable them.

After you have completed this activity, you will delete all created resources, then verify with screenshots.

Do not create any resources unless you are specifically requested to. This runs a very high risk of your student account credits ($100 cap) being spent in their entirety, at which point you will no longer be able to access any of the resources required for this course, and future courses.

In this lab, you will be provisioning:

• One (1) Resource Group
• One (1) Storage Account
• One (1) Storage Blob
• One (1) App Service Plan
• One (1) App Service

As you progress through this activity, your instructor may request that you capture a screenshot periodically (on Mac OS: “command+shift+3” to capture the whole screen, or “command+shift+4” then drag the cursor over the area you would like to capture). These screenshots are part of your required deliverable and will be graded.

Please attend or view Live Lecture (Week 3 Part 1) when available for the latest walkthrough. It is important to understand Cloud Service Provider (CSP) platforms change frequently, so the available recording here may look differently than what you see. You are welcome to use your best judgement to navigate any differences, or wait until the Live Lecture recording becomes available for further elaboration.

Host a Static Website via Storage

1. Create a new Resource Group
   1. Region: East US 2
   2. Name: CNW-WEB
2. Create a new Storage Account
   1. Resource Group: CNW-WEB
   2. Storage Acct Name: “firstinitiallastname”web
   3. Location: East US 2
   4. Performance: Standard
   5. Account Kind: StorageV2
   6. Replication: Locally Redundant (LRS) or no redundancy, if available
   7. Access-Tier: Standard (Whichever option is least expensive, this is considered Cool storage)
      
3. Create a Static Website from within the Storage Account
   1. In the sidebar, under “Data Management” click “Static Website”
   2. Click “Enabled”
   3. Index Document Name: “index.html”
   4. Note the Primary Endpoint URL (this is the public URL to access your static website)
   5. Access “$web” container and upload “index.html” (download the .zip below and extract)
   6. Leave upload blob setting as their defaults
4. Access your static website via the Endpoint URL (great color, huh!?) – screenshot
5. Return to to “Data Management > Static Website” and click “$web” to access the container
6. Click “Index.html” then select “Edit Blob”
7. On line 19, change the “bgcolor” Hex value to “FFFF00” (yellow) and click “Save” – screenshot
8. Access your website URL to see the changes (you may need to reload a few times)

• 1 KB

Host a Website via Server-less App

1. Create an App Service Plan
   1. Name: “firstinitiallastname“web
   2. Resource Group: CNW-WEB
   3. OS: Windows
   4. Location: Central US
   5. Pricing Tier: F1 Free
2. Create an App Service
   1. Name: cnw1″firstinitiallastname“
   2. Resource Group: CNW-WEB
   3. App Service Plan: The plan you just created (should be selected by default)
   4. Application Insights: Disabled
   5. OS: Windows
   6. Runtime Stack: .NET Core 2.1 (or the nearest version if 2.1 is not available)
3. Configure App Service to display static website
   1. Navigate to your storage blob website
   2. Right click on the page, and select “View Page Source”
   3. Select all (cmd+a), then copy (cmd+c)
   4. Navigate back to your App Service
   5. In the sidebar, select “Development Tools > App Service Editor”
   6. Click “Go”
   7. Select “WWWROOT > hostingstart.html”
   8. Select all (cmd+a), then paste the copied html from step C
   9. On line 19 or 20, change the “bgcolor” hex value to “F00200” (red)
   10. Navigate to the App Service’s public URL (which can be found on the overview page) – it should be “cnw1firstinitallastname.azurewebsites.net”

Required Screenshots

The following screenshots should show the configurations identified in lab, for each component:

1. Storage Account
   1. Overview page
   2. Static Website page
2. Browser displaying the blob-hosted website (purple) – be sure to capture the entire browser window
3. Browser displaying the blob-hosted website (yellow) – be sure to capture the entire browser window.
4. App Service Plan Overview page
5. App Services
   1. Overview page
   2. App Services Editor displaying HTML for the hosted website
6. Browser displaying the App Services-hosted website (red) – be sure to capture the entire browser window
7. All Resources page showing that all resources have been completely deleted (it should be empty)

There should be 9 individual screenshots.