Closed sevab closed 10 years ago
Hey guys!
Firstly thank you for the update about today's lecture Seva - I could not make it due to mysterious circumstances. However, I will make sure I go through the slides today but can we meet tomorrow (Wednesday, 22nd January' 14) since I think all of us are either free or have half a day at uni? We can make an attempt at making those diagrams and correct ourselves from what we learn in Thursday's workshop?
Not a compulsion though, just a suggestion if you all think it's ok.
@akshay378 Yep, I'm free Tomorrow after 14, so if @hornets (Vlad) and @armand64 can make it as well, let's do it! Otherwise Thursday or Friday is cool as well! Also, Akshay and Armand, bring your laptops and I'll show you how to use git so you guys know how to push code when we'll be doing the 3rd part of the coursework. If you remember git is a version control system that will allow us to collaborate together on the same codebase without having to email each other folders with code. All the code that we push will then be seen here on github.
I have an interview at 2p.m Tomorrow. So any day except Tomorrow would be good for me.
Lets keep it on Thursday then since Armand is not free tomorrow. @sevab I learnt quite a bit of git while doing the last piece of coursework for Software Development last term from @hornets but yeah it will be refreshing to go through it again and gear ourselves up for this coursework!
Sup guys! I think we could easily split the work by meeting on Sunday, doing a few Use Case Scenarios together just so everyone knows how to do them. We could then split the Use Case Scenarios between each other, complete them in 2-3 days individually, meet again and make any corrections as a group.
I think the logical way would be for all of us to discuss and work in the same room. Remember this is a group work that simulates real life production. But there’s a bigger issue I just checked and StarUML is not cross-platform and development looks dead to me. Do we have any mac alternatives suggested by David?
P.S: Why is this package public??
@hornets, yeah we can work together as well. Though as David has mentioned we would still have to write any of the questions we have to each other on Github. Regarding StarUML, there was no alternative suggested by David, but a quick google search led me to ArgoUML which has some positive reviews and has many of the StarUML features. I've used it today, and it seems to be a perfect substitute. Yeah, I'll make the package private right now.
On Friday, 24 January 2014 at 10:20, hornets wrote:
I think the logical way would be for all of us to discuss and work in the same room. Remember this is a group work that simulates real life production. But there’s a bigger issue I just checked and StarUML is not cross-platform and development looks dead to me. Do we have any mac alternatives suggested by David? P.S: Why is this package public??
— Reply to this email directly or view it on GitHub (https://github.com/sevab/picture-house/issues/2#issuecomment-33211674).
Hey guys, those of you who aren't very familiar with git, how it works and how to use it, here's an excellent interactive tutorial that I used myself to learn git. It would be great if you learnt the basics before we start coding on the project (i.e. ASAP this week). And if you still have any questions feel free to ask me. Also, you can probably find the answers to many of your questions in the official Git Guide here. You can also use this guide/book if you prefer learning by reading rather than by doing an interactive tutorial.
Git is used extensively in the industry, so once you learn it, I recommend that you put it on your CV (along with 'experience using GitHub') and be sure that your employer will appreciate and value this skill.
One more thing, in the tutorial you are working with a fake Terminal app, while to use git on your computer just open the real Terminal app and use it just as you did with the fake Terminal in the tutorial. @armand64 @akshay378 @hornets
Hey guys! So I've rewritten the specification in terms of bullet points here. Feel free to make any corrections by clicking the edit button. Everyone can edit everything on this repo (repository). Since we have to discuss everything here and submit this discussion with the coursework, please write all your questions, opinions and propositions below instead of Facebook. Also, I think we are required to document the outcomes of our offline meeting discussions here as well. Anyways, now that I discovered that there's coursework specification on page 2, I think we should meet sometime after today and attempt to draw some diagrams. On Thursday there'll be a lab where we'll do some diagrams, so I propose that we meet after Thursday. Also, since none of you were in class today, I suggest you read through the slides about the diagrams, since that's what we'll pretty much have to do for this coursework.
Here's a reminder of what this coursework is about:
Backend: Requirements Analysis and Specification Hand-in: Week 4, Term 2 (February 3rd, 2014). Duration: 20 hours. Value: 20%. Product: a description of the requirements of the prototype computer system in the form of use case diagrams with accompanying textual scenarios. Process: a record of the evolution of the requirements in the form of a printed copy of the discussion that took place on Google Code.