F27SB 软件开发

Posted 2023-05-31 pyzlx96

F27SB Software Development 2
GUI Coursework 1: LayoutManager
Create a digital clock
a) Create the layout for your digital clock. The clock should have the following
layout:
so:
● HH - displays the hours
● MM - displays the minutes
● SS - displays the seconds
● AM/PM - displays whether it is before (AM) or after mid-day (PM).
The hours/minutes/seconds should be displayed in 36 point, italic serif.
(Correct layout: 0.25P,
Class extends JFrame: 0.25P,
Class follows OOP principles: 0.25P,
Global set-up in main method: 0.25P)1
b) Make the clock show the current time. For this you should use the Calendar
class from java.util with:
● Calendar.getInstance() - create Calendar object for current date/time
● get(field) - return integer field from Calendar object, where field may
be Calendar.HOUR, Calendar.MINUTE, Calendar.SECOND,
Calendar.AM_PM, etc.
● the value returned from Calendar.AM_PM may be compared with the values
Calendar.AM and Calendar.PM to determine if it is before or after mid-day
Create a function that runs continuously and updates the display to always show
the current time.
(Clock is updated when programme starts: 0.5P,
Clock is continually updated: 0.5P)
For more information about this class, see:
https://docs.oracle.com/javase/7/docs/api/java/util/Calendar.html.
1 Detailed explanation of points at the bottom of the document.
Create a progress meter
a) Many GUI applications have metres that indicate the progress made so far
towards completing an activity代写 F27SBas a percentage of the anticipated total activity.
Write a program to display a progress metre as follows. The metre consists of a
window with a column of 11 labels. The first 10 labels indicate progress steps of
10% and are initially red. The bottom label shows the amount of activity remaining
as a textual percentage, and is initially set to “0%”.
(Correct layout: 0.25P,
Class extends JFrame: 0.25P,
Class follows OOP principles: 0.25P,
Global set-up in main method: 0.25P)2
b) Create functionality to simulate steps of 10% progress. For this the user
repeatedly presses return on the console inside Eclipse (use a Scanner object
for this). Every time, the top-most red label is changed to green and the progress
label value is incremented by 10 until that value is 100%. Make sure that no errors
occur if the user tries to go past 100%.
(Progress is shown when pressing enter: 0.5P,
Program stops reacting when 100% is reached: 0.5P)
Example output:
2 Detailed explanation of points at the bottom of the document.
Marking
In each coursework, you can achieve a total of 4 points. Each question awards different
amounts of points for different parts of the question. Partial completion of a task will
award the partial points listed underneath. Most descriptors of points are self-explanatory
in context of the task. Where further clarification is needed, you can find that below.
Your work will be checked by a lab helper during your assigned lab slot. Once all tasks
are checked, the points will be used to calculate your marks. Please, understand that the
lab helpers are not marking your work but are checking the completion of subtasks. As
part of this check, you will need to explain how you solved the given task. Only
successfully completed sub-tasks will award points.
The marks will be released on Canvas after the marking deadline has passed. This is not
an automatic process so please, be patient. Once the marks are released, you will be
notified via Canvas. Please, make sure to check your marks as soon as possible. If
there are any issues, please contact your teaching team immediately.
Collusion and Plagiarism
As mentioned above, you will need to explain your work during the demo session in the
lab. If you are not able to explain how you arrived at the solution to the task, we need to
assume that you did not do the work yourself. We do, however, know that you might be
anxious or nervous during the session. Please, rest assured that this is not an
interrogation and you can take all the time you need to explain your solution.
If there is reasonable doubt that you solved the given problems yourself, you will not get
any points for this task. If there are concrete indications that you copied your answer or
colluded with other students, we might also start an official investigation.
Please, make sure to fill and sign the Declaration of Student Authorship form for
each coursework and upload it to Canvas. If you do not upload the form, we will not
be able to give you any marks for this coursework.
If you feel unjustly accused of plagiarism or collusion, please contact your teaching team.
Coursework submission
Unless stated otherwise, all code parts of your work need to be committed and pushed to
your GitLab fork. You need to upload the Declaration of Student Authorship to Canvas,
and you need to present your solution to a lab helper. If you fail to do any one of these
steps, you will not be awarded any marks.
The deadline for submission can be seen on Canvas. You will need to present your
work to a lab helper any time before the deadline during your allocated lab slot. If
you do not manage to present your work before the deadline, you can do so at the first
lab after the deadline but will incur a 30% late penalty. If this late submission was caused
by issues out with your control, you can apply for mitigating circumstances to have this
late penalty removed.
If you also fail to present your work at the lab following the deadline, we will not be able to
give you any marks for your work. Similarly, if this was caused by circumstances out with
your control, you should apply for Mitigating Circumstances.
Please, note that we are not allowed to give individual extensions. If you cannot
submit your work on time, you will need to apply for Mitigating Circumstances.
Explanation of Points
Correct layout: Where an image or text explanation of the layout is given, points are
awarded for exactly achieving the required layout. You are free to choose a different
layout that you find more appealing as long as all the same components are used. This
means you might want to choose a different layout manager or different positioning but
you should still make sure to have the same amount of labels, panels, buttons, etc. If an
example of a layout is given, you are required to match this layout as closely as possible.
Class extends JFrame: The class that declares and initialises all the GUI components
should be a subclass of JFrame and correctly use the methods and variables provided by
its super class to achieve the desired layout.
Wrong Wrong Right
public static void main()
JFrame f = new JFrame();
f.add(new JLabel());
…
public class A
public A()
JFrame f = new JFrame();
f.add(new JLabel());
…
public class A extends JFrame
public A()
add(new JLabel());
…
Class follows OOP principles: You should endeavour to reduce coupling and increase
cohesion in your code. That means you should check that every class is responsible for
its own components and data and that you do not provide unnecessary public variables or
methods. Always think about how someone else could use your class in a different
project. Refer to all the guidance given in the first half of the course and make sure to
highlight this to the lab helper when explaining.
Global set-up in main method: When you think about someone using your code in their
larger GUI, do you think they are happy that the name, size, position, and visibility is
defined inside the class where it cannot easily be changed? Make sure to only define
these things in the main method where you create a new instance of your class as we do
in the lectures.

 WX：codehelp

软件开发环境简介

参考技术A

软件开发环境SDE（Software Development Environment）是指在基本硬件和宿主软件的基础上，为支持系统软件和应用程序的工程化开发和维护而使用的一组软件。在实际软件开发过程中一般包含三个阶段：开发—>测试—>上线,根据每个阶段处理的业务功能不同，其所处的环境也不同。

例如 dev/test/beta/release/stable 其实也是对应以上分类.

开发环境dev：(development)开发环境

开发人员直接使用的环境，用于开发的服务器配置比较随意，为了方便开发调试方便，一般打开全是错误报告和测试工具，是最基础的环境，开发环境的分支一般为feature分支。

联调环境locat：

开发环境，需要一定的稳定性，部署在本地服务，因为现在的项目绝大多数都是前后端分离的，因此需要进行前后端接口的联调，保证参数传递正常，而且在spring boot项目下很多子项目之间有互相调用接口的也需要进行联调。

测试环境test/sit：(system integration testing)系统集成测试（内测）

系统集成测试是评估产品在其规格范围内的环境下工作，能否完成产品设计规格所需要的功能和周边设备。应用软件的兼容性。大致上分为硬件兼容性测试、软件兼容性测试、认证测试等。

硬件测试：如cpu、dimn、storage、nic、usb等测试

软件测试：操作系统兼容性测试、驱动安装测试、配套软件安装使用测试

认证测试：windows、vmware等认证

验收环境uat：(user acceptance test) 用户接受度测试环境（外测）

系统开发生命周期方法论的一个阶段，这时候的用户或相关测试人员根据计划和结果对系统进行测试和验收，他让系统用户决定是否验收系统，是一项确定产品是否能够满足合同或用户所规定的需求的测试。

压测环境pet：(performance evaluation test)性能评估测试环境（压测）

分为负载测试、容量测试、压力测试

①负载测试：关注用户数量和性能指标；

②容量测试：检测最大用户支撑的数量；

③压力测试：高压力，看系统如何崩溃，准备预案。

生产环境prod：(production)真实环境

是指正式提供对外服务的，一般会把错误报告关掉，打开错误日志，是最重要的环境，部署分支一般为master，是普通用户能直接接触到的环境，如果生产环境出现差错，那么将直接导致公司出现名誉受损和财产损失。

参考: https://www.cnblogs.com/huangrizhang/p/10925462.html