159.251 - Software Design and Construction

雅思听力词组总结 雅思听力词组总结(涵盖几乎所有雅思真题词组)已更新至1037条 阅读详情


Massey University
159.251 - Software Design and Construction
Assignment 1
Deadline and Late Submission Penalties
You must submit your final work using the stream submission system no later than 9 October
2024 at 11.59 pm. The penalty is 20% deducted from the total possible mark for every day
delay in submission (one day late – out of 80%, two days late then out of 60% … etc.).
You are expected to manage your source code and other deliverables using version control.
“The Cat Ate My Source Code” is not a valid excuse for a late submission.
Contribution to Final Grade of the Course: 22%
Please read carefully, as there are many parts that you should be aware of.
Overview
You are to work in self-selected pairs (i.e., select your teammate) to create the program
defined below. You will need to use git to manage source code contribution and integration
between the two members. All project issues and changes should be tracked using an issue
tracker (set up within your repository).
Note: Both group members will receive the same mark unless it is clear that the work is
predominantly that of a single person. These will be sorted out on a case-by-case basis. The
partition of the work is entirely up to you and your project partner.
Part of this assignment is to become familiar with using git for version control. You must use
GitHub for this assignment, and the repository must be private.
IMPORTANT: use the following conventional name for your repository: 251-Assignment1-
2024-FirstName1-FirstName2. For example, if the first student is Sarah and the second
student is Li, then the repository name should be (251-Assignment1-2024-Sarah-Li).After submitting your assignment on Stream, you must send an invitation to your GitHub
repository to one of our markers. After the submission is completed, one of the markers
will contact you to request access to your repository.
Tools Required
● IDE independent: You may develop this in any IDE or code editor you like! The tools
included here are available for major IDEs and Maven dependencies.
● Git and GitHub(for version control)
● GitHub Issue Tracker (for log changes and bugs)
● Maven (for dependency management and process automation)
● A code metrics tool
● Docker for packaging
● PMD (for code quality check)
● other libraries to perform the different functionalities (you are free to search and use
any library that will help in implementing any of the functionalities).
Tasks
1) Developing a text editor program using Java – see details below.
2) Source code and version control:
a) create and maintain a git repository on your local machine for your source code
and on a remote repository to provide a central server accessible to both
members and also accessible for marking.
b) keep an audit trail of commits in the git repository. These will inform part of
the marking.
c) make sure that you actively (almost daily) use git features such as branching
and merging (not only on the last day before submission!).
d) write your configurations in YAML file. You must submit at least one
configuration file that works with the text editor. This could be a file with the
default parameters for the text editor, such as the default text format or default
font colour.
3) Log changes and bugs: keep track of changes and issues – use an issue tracker as
part of your version control. Please use the same issue tracker that is provided by your
Git project hosting site (i.e., the “issues” feature in GitHub). This has to be actively
used!
4) Automation: automate your process so it is easier to load files and generate reports.
Use Maven to declare all dependencies. If you are using any external libraries, do not
include any jar files with your submission but add them as Maven dependencies! Also,
don’t try to change your Maven files into a different format. The pom file should be an
XML file.
Build those Maven build tasks in your Continuous Integration (CI) pipeline using GitHub
Actions. Make sure that the configuration (YAML) file is correctly added.
5) Readability: ensure you write clean code, correctly handle exceptions, and add
comments to explain your code. Make your code “human-readable!”.
6) Quality: check the quality of your code and outputs
2a) use code quality tools to report metrics data of your program. The metrics report
generated from your code should be submitted. The process should be
automated and included in your Maven dependencies (see Section 2 below).
b) (Bonus) Write unit tests using JUnit to test (at least) the following functionalities:
open, save and search (see details below).
7) Deployment: package your project and deploy it into a Docket container (a Windows
or Linux container). This must allow the markers to run the Maven project from the
Docker container (without the need to install or configure the environment). Make sure
to include your Docker file with your project, and to include details on how to load and
run your container in the README file.
Make your own text editor!
1. The Text Editor
Your program is basically a standard text editor (or text processor) – something similar to
Notepad, Atom, or Geany. The editor should allow you to write text on it using standard text
encoding formats (i.e., ASCII/UTF-8). You should develop this program in Java. Note: a
standard text file (mostly) does not need any additional metadata files to assist the reader in
interpretation,
The main functionalities of the text editor are:
- Full GUI access to the application
- Create a menu of options at the top of the editor, similar to the following
The menu should (at least) include the following sub-menus: File, Search, View, and Help
- Implement the following functionalities:
o New function: to create a new (fresh) window.
o Open function: to read other text files (just standard .txt files). This should
allow users to navigate the file system to select\search for a file.
o The ability to read OpenDocument Text (.odt) files. This is part of the Open
function.
o Save function: save text output into .txt file format. This should allow users to
navigate the file system to save the file in a selected drive/location.
o Search: search for text within the screen (this will be tested based on a single
word)
o Exit: to quit the program – close all windows.
o Select text, Copy, Paste, and Cut (SCPC) capabilities.
o Time and Date (T&D): retrieve the current time and data from the OS and
place it at the top of the editor's page.
o About: display the names of both team members and a brief message in a
popup message box.
o Print function: allow your editor to print text by connecting it to the local printer
in your machine (similar to any other text editor you have used).
3Harder functions
● ability to read source code files such as .java, .py, .cpp or similar. different
syntax should be shown in different colours. For example:
● reading and displaying other file formats beyond txt and source code files:
mainly, Rich Text Format (RTF) and OpenDocument Text (ODT) format.
Hint: you can use an external library to do so.
● include a PDF conversion function in your editor, so the file can be saved in
PDF format (for standard text files). Use an external library for this, such as
Apache PDFBox.
Note: There is no specific requirement regarding which GUI library you should use, but try to
make your program as cool as possible!
2. Code Quality and Management
Once development is done, you must report metrics data using a metrics tool. You may use
a software metrics tool (see some examples above). Code quality report from PMD should
also be submitted with your assignment.
a) generate a metrics data report from any software metrics tool (see below for the
specific metrics) and add the report file (.txt or html) to $project$/reports/metrics
b) create a new maven goal called “pmd” that should generate a metrics report using
PMD (see below for the specific metrics) and add the report files to
$project$/reports/pmd.
● Code Size (per class): Lines of Code (LOC) and Number of Methods (NOM)
● Code Complexity: Cyclomatic Complexity and code coupling metrics
(Coupling Between Objects (CBO) OR Efferent Coupling).
● Code Quality Report from PMD. Use only Java Basic rules such as Naming
Convention for classes and variables (extract the full report and include it with
your submission).
Submitting your assignment
45
Submission must be completed on Stream using the Assignment submission site.
Share your program on your private GitHub repository with us by sending a share
invitation to the user. This is to track commits on your Git repository.
Include a README file in the top level of the project
The Readme.md is a file with a Markdown syntax (this should be correctly formatted
as a markdown) that contains:
1. the names & IDs of BOTH MEMBERS of the group.
2. clear instructions on how to run your program and if there are any other
directories, what they contain.
3. for each student, a couple of the most significant git commit IDs show the
work of each individual member of the group.
4. a link to your private GitHub repository. A marker will contact you after
submission to request access to the repository. Note: there will be a penalty if
the repository is found to be public.
Who submits what?
Only one member of a group should submit a complete project, the other just submit
the Readme.md file:
● member A: submit (through Stream) a single compressed (e.g., zip or tar) file
that contains the assignment (Maven project files and other configuration
filess without the /target directory)
o name the compressed file with both members’
FirstName_LastName and ID numbers (e.g. Xiaofeng_Liu-87878787-
Susan_Jones-01010101.zip)
● member B: submit just the README.md file containing your name and that of
the partner who is submitting the zip/tar file. This is so Stream knows that
you've submitted something.
Markdown Quick guide
https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing
and-formatting-on-github/basic-writing-and-formatting-syntax6
Assessment

Git Rebase 详解与实战使用指南 本文系统讲解 Git Rebase 的原理与实战,揭示其如何通过线性化提交历史提升代码可读性。对比 Merge 与 Rebase 的差异,详解基础用法、交互式变基(如 squash、reword)、冲突处理及常见陷阱。强调“仅对本地分支 rebase”“强推用 --force-with-lease”等最佳实践,并推荐使用 git pull --rebase 保持开发主线整洁,助力团队协作高效有序。 阅读详情

相关推荐

【信息科学与工程学】【数据科学】数据科学领域——第三篇 数学08 几何学00总篇

编号英文名称中文名称简要说明/归属1Foundations of Geometry几何基础公理化方法, Hilbert《几何基础》2Euclidean Geometry (Synthetic)欧几里得几何(综合法)《几何原本》传统3Analytic Geometry解析几何坐标方法, Descartes, Fermat4Plane Geometry平面几何三角形、圆、共点共线等经典问题5Solid Geometry立体几何三维空间中的图形与度量6Non-Euclidean Geometry非欧几何平行公设不

weixin_49199313的博客 220

159.251 Software Design and Construction

OverviewThe toolsTasks).used!Also,XML file.”.function.word)45。

ishtttsynt的博客 732

bcftools学习笔记(一)

欢迎关注"生信修炼手册"!本篇主要介绍index, view, query, sort, reheader这五个命令。1. indexindex命令用于对VCF文件建立索...

庐州月光的博客 6013

告别规则黑盒:基于JVS-Rules的风控规则治理实践——可视化决策编排+血缘追踪+版本快照

可读’——通过决策流图谱与业务语义节点,让非技术人员理解逻辑;‘可溯’——依赖规则版本快照与执行日志,实现任意交易的全链路回放;‘可担责’——基于血缘追踪与权限基线,清晰界定业务定义、技术实现、合规验证三方责任。这三者共同构成风控规则治理的三角支柱,将隐性经验转化为可版本化、可审计、可协同的组织级数字资产。

weixin_42054392的博客 448

保姆级教程:在Ubuntu 20.04上搞定pybind11,解决‘找不到头文件’的坑

本文提供了一份详细的Ubuntu 20.04下pybind11配置指南,重点解决常见的'找不到头文件'问题。从环境准备、安装策略到三种专业解决方案(修改CMakeLists.txt、环境变量方案、绝对路径包含),帮助开发者高效搭建C++与Python的桥梁。

weixin_28829325的博客 285

微软登录OAuth 2.0授权流程

OAuth 2.0是一个关于授权的开放网络标准,它允许第三方应用获取用户数据,是目前最流行的授权机制。微软身份平台支持OAuth 2.0授权码流程,使得客户端应用程序能够获得对受保护资源(如网络API)的授权访问。这一流程在保障用户数据安全的前提下,实现了应用的便捷登录与数据共享。当用户在一个支持OAuth 2.0的应用上,希望使用微软账号进行登录时,OAuth 2.0授权流程即被触发。

qq_36569837的博客 4094

把 KV Cache 压到 FP4:BitDecoding-FP4 的算法-系统协同设计复盘

长上下文推理卡在KV Cache的显存与带宽上,而现有FP4方案要么精度崩、要么速度废。这篇文章复盘BitDecoding-FP4如何用三个算法补丁加一个系统重构,在B300上把服务吞吐提升2.4–3.0倍,精度几乎不掉。

helloagent的博客 317

华为使用MicroG安装并使用Google服务教程

鉴于众多华为手机用户因无法使用Google服务而感到不便,我经过多次摸索和测试,总结了一份简单易懂的教程,希望能够帮助到大家。无论是需要使用Google Play商店下载应用,还是需要使用Google服务进行工作和学习,本文将详细介绍如何在华为手机上安装并使用Google服务。二、前置条件软件要求:Aurora Store(替代Google Play商店)、MicroG Companion、MicroG Server(替代Google框架)

weixin_41926602的博客 3万+

Git 工程化与内部原理完全指南:Hooks / LFS / 对象模型

本文深入解析 Git 工程化核心:通过理解内容寻址的对象模型与引用机制,掌握 Hooks(pre-commit、pre-push 等)实现自动化校验,借助 Husky 实现团队统一配置;使用 Git LFS 高效管理大文件,避免仓库膨胀;深入 .git 目录结构,理清 blob/tree/commit 三类对象与指针关系。强调“先自动化、再靠人”的工程原则,结合命令速查与实战 Checklist,助开发者从“会用”跃升至“懂它、能改造它”的境界。

qq_28112995的博客 346

4路QSFP28接口能玩出什么花样?基于璞致VU13P开发板的100G网络测试方案

本文详细介绍了基于璞致PZ-VU13P-KFB开发板构建100G网络测试方案的实战指南。该方案充分利用板载Xilinx Virtex UltraScale+ FPGA的强大算力与4路QSFP28接口,涵盖从光模块选型、Aurora协议配置、开源Corundum方案部署,到误码率测试及散热优化的全链路流程,为高速网络设备研发与验证提供了可靠的硬件平台。

cola5的博客 457

AI 大模型在电商精准营销中的应用

例如,对于用户 A 和用户 B,通过比较他们对共同评价过的商品的评分差异来确定相似度。其中,(Gain(D,a))表示特征(a)对数据集(D)的信息增益,(Ent(D))表示数据集(D)的信息熵,(V)表示特征(a)的取值个数,(D^{v})表示特征(a)取值为(v)的样本子集。其中,(sim(A,B))表示用户 A 和用户 B 的相似度,(I)表示用户 A 和用户 B 共同评价过的商品集合,(R_{A,i})和(R_{B,i})分别表示用户 A 和用户 B 对商品(i)的评分。(三)营销活动效果预测。

alittlehippo的博客 1627

Windows 11 WSL2 网络代理连接问题排查与完整解决方案

针对 Windows 11 下 WSL2 无法连接宿主机代理及 Connection refused 报错,先通过 .wslconfig 开启 镜像网络模式(mirrored) 与 自动代理(autoProxy) 打通网络环境。随后按需二选一配置桌面代理客户端:日常开发推荐开启 Allow LAN(允许局域网连接) 配合系统代理,轻量且免管理员权限;针对无视环境变量的终端工具,则以管理员身份开启 TUN 虚拟网卡模式 底层接管流量,即可实现 WSL 顺畅联网。

weixin_43379230的博客 180

华为OD机试 - 商品推荐多属性排序 - 数组(Python/JS/C/C++ 双机位A卷 100分)

本专栏收录于《华为OD机试真题(Python/JS/C/C++)》。刷的越多,抽中的概率越大,私信哪吒,备注华为OD,加入华为OD刷题交流群,每一题都有详细的答题思路、详细的代码注释、3个测试用例、为什么这道题采用XX算法、XX算法的适用场景,发现新题目,随时更新。双十一来临,小王准备买某个购物平台买坚果。在输入坚果时,页面默认按照综合推荐列表。小王想知道这个综合排序时如何完成的,于是便开始思考算法题。经过一番操作后,完成它的多个关键词排序算法。希望你给小王提供一份正确的排序结果,验证其实现算法结果的准确性

学Java,找哪吒 623

多存储协同架构:JPA + MyBatis + Elasticsearch + Redis 的职责分工与通用实现

本文阐述了在高并发订单系统中,通过JPA、MyBatis、Elasticsearch与Redis的多存储协同架构实现职责分离:JPA负责事务性写操作与简单查询;MyBatis处理复杂联查与报表统计;Elasticsearch承载海量数据下的多维检索与聚合;Redis用于缓存、防回滚暂存及分布式锁。各存储分工明确,通过异步同步机制联动,兼顾一致性、性能与扩展性,构建高效稳定的系统架构。

BADAO_LIUMANG_QIZHI的博客 276

【报错】open /var/lib/docker/tmp/docker-import-863402796/bin/json: no such file or directory

然后,通过docker images可以看到镜像已经加载进来了。然后,通过docker images可以看到镜像已经加载进来了。

静谧、淡雅 6228

精雕软件(JDpaint) 5.5 绿色版

精雕软件(JDpaint) 5.5 绿色版精雕软件(JDpaint) 5.5 绿色版精雕软件(JDpaint) 5.5 绿色版

Elasticsearch 9.x 从入门到精通(5/7):集群、分布式与运维

《Elasticsearch 9.x 从入门到精通》共 7 篇,本篇为第 5 篇,覆盖第 21~26 章。:Elasticsearch 9.x 源码 main 分支()与官方全量文档。:每个知识点标注官方文档出处,涉及实现原理均给出源码锚点路径:行号,禁止编造 API。

Chdaring的博客 329

Data-Structures-and-Algorithm-Analysis-in-Java.pdf

作者: Weiss, Mark A. 出版社: Addison Wesley Data Structures and Algorithm Analysis in Java is an “advanced algorithms” book that fits between traditional CS2 and Algorithms Analysis courses. In the old ACM Curriculum Guidelines, this course was known as CS7. This text is for readers who want to learn good programming and algorithm analysis skills simultaneously so that they can develop such programs with the maximum amo...

Elasticsearch 9.x 从入门到精通(1/7):初识 Elasticsearch

官方定义(开篇):身份能力对应源码模块分布式搜索/分析引擎近实时全文检索、聚合分析index/可扩展数据存储海量文档存储、快照、生命周期cluster/向量数据库kNN 语义检索、混合检索(kNN)+x-packElastic 官方将能力组合为四类"解决方案"():Elasticsearch(搜索)、Elasticsearch Vector Database(向量/Serverless)、Observability(可观测)、Security(安全)。核心搜索能力在所有形态中共用。

Chdaring的博客 187

VC中sqlite的使用

在VC中对sqlite的使用,实现数据库大批数据的快速插入,读取数据库中的数据在ListCtrl中显示

计算机控制技术及应用

《计算机控制技术及应用》通过总结作者的科研成果和吸收国内外的先进理论、方法和技术,以计算机控制系统的网络化、开放化、智能化和集成化发展趋势为主线索,主要介绍计算机控制系统的基本概念和计算机控制系统的典型形式,计算机控制系统的数学描述与基本分析方法,以及数字PID控制器、最少拍控制系统、达林算法、状态变量设计法等设计方法及其各种改进算法。重点突出计算机控制系统输入输出通道接口的设计方法和典型控制系统的设计案例与实现方法等。

使用 SpiceDB 为 Elasticsearch 检索增强生成实现细粒度授权

本文介绍如何在Elasticsearch检索增强生成(RAG)流程中实现细粒度访问控制。通过SpiceDB基于关系的访问控制(ReBAC),将权限逻辑从应用代码和kNN查询中剥离,转为在关系图中管理用户与文档间的权限。利用SpiceDB在检索后过滤内容块,确保大语言模型仅接收授权数据,防止敏感信息泄露。该方案支持灵活的逐文档共享、跨部门访问及例外授权,无需重构角色或重新索引。结合LangGraph构建确定性授权节点,强制执行安全边界,抵御提示注入攻击。推荐生产部署时采用超额检索、元数据预筛选与权威数据源同步

Elastic 中国社区官方博客 313

点过“不再询问”就要检查:Claude Code权限文件也可能存着密钥

Apiiro报告揭示带密钥的命令可能进入Claude Code权限文件。结合独立Git实验,解释local配置、忽略规则与历史泄露的区别,以及发现问题后的处理顺序。

2301_76711398的博客 208

Elasticsearch 9.x 从入门到精通(4/7):聚合分析与文本分析

analysis.*定义组件和 analyzer,mapping 把 analyzer 绑到字段。},},},},},"title": {先测试组件,再绑定字段。用_analyze验证 token,不要只靠真实查询猜。text 与 keyword 并存。排序、聚合用keyword子字段,全文检索用 text。stemming 与精确展示分离。索引 stemming token,展示仍用_source原文。stop words 谨慎。

Chdaring的博客 295

【一次 Elasticsearch 高基数聚合慢查询的定位与优化】

当Elasticsearch聚合查询首次执行慢、后续迅速恢复正常时,问题往往不在数据量本身,而在于全局词典构建开销。通过Profile分析发现,虽聚合耗时仅几十毫秒,但首次请求整体耗时达1秒以上,表明瓶颈在初始化阶段。结合keyword字段使用Doc Values的特性,可推断为首次访问时需加载全局词典(global ordinals),导致延迟。开启eager_global_ordinals可将词典预加载至内存,显著降低首次查询延迟,尤其适用于高基数聚合场景。此案例揭示了“首次慢、后续快”问题的典型根因及

大雪冬至的博客 386

如何用 STAROps Elasticsearch 智能助手看穿“搜索变慢”

某电商平台的商品搜索服务使用一台 6 个数据节点的 Elasticsearch 实例。周五北京时间 20:00 起,业务陆续反馈搜索变慢。业务监控中的搜索接口 P99 从平时约 200 ms 升到 2s 以上,部分请求超时。值班工程师打开控制台:集群状态为 Green,没有未分配分片,集群平均 CPU 约 40%,乍看不像资源已经吃紧。

阿里巴巴云原生的博客 350

Git撤销修改三重境界:从工作区到版本库全解析

区域英文说明工作区你直接编辑文件的地方,肉眼可见的代码。暂存区执行git add后,代码进入的区域。版本库Repository执行git commit后,代码被永久存储的区域。什么是撤销修改?当你在工作区写了一段时间代码,发现新代码质量极低,甚至无法继续开发时,将代码恢复到上一个提交版本(那个干净、整洁的版本),基于旧版本重新开发,这个回退操作就称为撤销修改。它能保证效率,也能避免烂代码污染项目。问题现状你的位置选择命令注意事项只在文件中改了,没add场景一--不可省略,别手动删。已。

江屿风的博客 860

[git]一次 Git push review 导致 Mac 卡死:10GB 仓库、自动 repack 与大文件 delta 压缩

日期:2026-11-15环境:macOS / Git 2.54.0 (Apple Git-157) / 24GB RAM / 12 CPU+ 子模块(Gerrit 评审流程)

AsiWorld的博客 222

Qwen2.5_PyQt5_情感分析桌面应用实战

使用 Git LFS 下载模型权重;使用 Transformers 在本地加载 Qwen;正确截取模型新生成的 token;使用 Qt Designer 制作桌面界面;在 Python 中连接信号与槽;使用后台线程避免界面卡死。对初学者来说,最容易混淆的是“界面”和“功能”的关系。这一句就是界面与程序逻辑之间的桥梁。完成这个项目后,还可以继续增加批量评价分析、结果导出、情感统计图、模型切换和历史记录等功能,把一个简单演示逐步扩展成真正可用的本地 AI 工具。

2302_80153299的博客 202

ElasticSearch vs MySQL:短链接服务中

在当今互联网中,短链接服务已成为许多应用场景的重要工具,例如社交媒体、广告推广、数据分析等。而面对海量数据的存储与高效检索需求,系统设计时常常面临一个关键问题:使用 ElasticSearch 还是 MySQL?本文将通过短链接服务的案例,从数据结构、查询性能、可扩展性等多个维度出发,对比分析两者的技术实现与适用场景,并为零基础开发者或在校学生提供清晰的选型建议。

后台模板 187
下一篇: HW 1: MATLAB
vx___codinghelp
博客等级 码龄2年 778粉丝 101原创
评论 1
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值