[190016] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Thinking Methodically about building a PoC

daemon@ATHENA.MIT.EDU (Hugo Slabbert)
Mon Jun 13 11:29:55 2016

X-Original-To: nanog@nanog.org
Date: Mon, 13 Jun 2016 08:29:51 -0700
From: Hugo Slabbert <hugo@slabnet.com>
To: nanog@nanog.org
In-Reply-To: <CAGcPvc-9k7VPk9XxnOi4TWiJn=++1t47iOybhVJD5cMw_w5v-A@mail.gmail.com>
Errors-To: nanog-bounces@nanog.org


--BXVAT5kNtrzKuDFl
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable


On Mon 2016-Jun-13 08:52:41 -0500, Possamai Rafael via NANOG <nanog@nanog.o=
rg> wrote:

>This may not be an answer very specific to your problem/question, but if
>you take a look at the following image, you will find a summary of what
>they called the engineering design methodology:
>
>http://www.cdn.sciencebuddies.org/Files/5083/9/2013-updated_engineering-me=
thod-steps_v6b.png

Seriously thought initially that you were going to link to:

http://i2.wp.com/tamingdata.com/wp-content/uploads/2010/07/tree-swing-proje=
ct-management-large.png

>You can adapt it to your circumstances, for example: instead of defining a
>problem in step 1, you can define a product, and after knowing what is
>expected from that product, you can then move to background research, etc.
>
>Hope that helps.
>
>
>Rafael
>

--=20
Hugo Slabbert       | email, xmpp/jabber: hugo@slabnet.com
pgp key: B178313E   | also on Signal

>
>
>On Sun, Jun 12, 2016 at 8:52 PM, Kasper Adel <karim.adel@gmail.com> wrote:
>
>> hi,
>>
>> I am asked to build a large lab/test it. I'm provided crazy scale numbers
>> for lots of technologies (L*VPN, IPv*, IGP*, All Tunnels flavors...etc).
>>
>> It took me a lot of time to build this lab, because when I got the
>> request/test plan handed over to me, I did not verify that these scaled
>> numbers are even possible, not to mention the combination. I assumed some
>> thought/research were done before.
>>
>> I'm trying to put together a list of the lessons learned, and the right =
way
>> to do this for future reference, specially that this project was time
>> critical and I got beaten hard because I did not deliver on time.
>>
>> So my question is, in your extensive experience, what is the right
>> method/approach to this kind of task:
>>
>> 1) Get started immediately (MVP), things will break, tune it along the w=
ay.
>> 2) Do some planning and research first.
>>
>> I'd appreciate any references to 'software engineering' or other
>> industries/
>>
>> Thanks
>>

--BXVAT5kNtrzKuDFl
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBCgAGBQJXXtFvAAoJEFsnhBAb2KmA9i0P/2OFMylFxzuhgAqYHZ4n+Wy2
qSXugHv2uJ8Nwlkp+DmcuOaYNjpGSsOR7NOQFFKN0h1CKhXrmEEDL/FE+rRTZwHh
dWKDPpPxRQ6dOZGnUhd+BTMmiOBd4z3g3D1F4JOVyKLbIbnNHsx6nkRiP/hu+eJf
WrWyxg7rR6WmXKoWXkCdtsioVVT8AZzXkiKd/KS60+IYSfziwWGlTJOEK+TbMyqX
VwxArAO/X/PmVb4QjR896m1jJkgOg/KyBNu9S46dVp1BZZooUh1F8WeK9F74f+y6
JVaybu4nfxxrrc8Xc2jNQY8UHIrDB0UkmhrgsTAlXOnEbYB4mzNqbByifzGPvvCs
ph1r7kQiHxLP7RsNjvqWfFsnxwCBaFnoF0aBy+Ohrz1PiIj41gq96PsjjvaXptDG
mNMgpcuPwtRLpqu7aByUq33kb4P4ZebGlP/GZ2nVi5zDF35iUx0hB0I79NshzMiP
e3icwQ/RNoCqoT0kK373EOk9IJAJOqKW3O2LvSCJ5ZCHCCuiaI2KyU/lUx/v8rRS
Y47hjIUwVO+SlHupxUvZ/x2Br4iAj3X5WKgS7vLrM9Jo5mxSHMSpDdv7XMPU8UbB
YfMOUPznVNP+iW5ZpWw4xp/3tt/PHyUi5sf/i8/f4HhuaC42P38DVIk0qOPPoBXx
lA8p7JZW6iCioXe6RPoP
=N3jx
-----END PGP SIGNATURE-----

--BXVAT5kNtrzKuDFl--

home help back first fref pref prev next nref lref last post